Displaying a structure record list and List Navigation

I'm using a Table Record widget to display a record list of structure records.

I also have a ListNavigation widget linked to the Table Record widget.

All seems fine, but when I click on the 'next' link it refreshes the record table, but does not move to the next set of records.  it appears to be a problem getting the Start Index value incremented.

How do you do that when using a structure record list (not a SQL data record list) ?

- Pete
Hi Peter,

In your Table Record what is the Start Index filled with?
It should be something like this: List_Navigation_GetStartIndex(YourTableName.Id, True)

João Rosado

I'm having exactly the same problem as Peter. And my start index is filled correctly as you can see. What else could be wrong?

Regards, Leen Rietveld.

I was running into a similar problem to what was initially described here and what I ended up finding was the problem was I didn't have an Ajax Refresh on my Navigation widget in the destination Screen Action. The index was getting set properly, but the UI wasn't showing that and it resulted in very strange behavior. Not sure if this is the same problem you were running into, but thought I would share what I ran into.

I am having the same problem too.

@Trevor, I AJAX Refresh the table wrapper container, which contains the table, list counter and navigation widgets. The widgets are updated but the table is not.

Two questions.

1. Are you getting the properties of the list navigation correct, like using the Count of the aggregate?

2. Are you refreshing the aggregate before refreshing the table records?

In any case, if you do a scafolding of an entity in the flow, it will create a page list and you can compare to see what are you missing.

Hi Jauch,

The problem only happens when the data source is a list of structures not from an aggregate. In my case it is the result from a stored procedure, it was copied into a local variable (of type list) and the local variable is used as the data source. 

And yes the properties are correctly set.

Hi Stanley,

The magic of the pagination only works out of the box with aggregates/queries.

If the list source come in a different way, you have to deal with it manually, guaranteeing that when the page changes, the table records source list is refreshed to contain only the records for that page.


Thanks for the clarification, this is what I suspected too.