I attach another example of this issue, where isFirst doesn't behave as I would expect.
The repeater has four columns:
Ref Num - sequential numbers 1-9
Item.index - That row's Item.index
Data - just some arbitrary data
Updated - shows whether a row has been updated
If you enter a character in the 'Enter data' column, the Data column will be changed for that row and the Updated cell will show 'true'.
First time: change the data for 2-3 rows including the first row then click the sequence of buttons:
- Only those items where updated=true will be visible.
- Only the first item will show.
- The Updated column for that one item will be changed to 'false' and the item will disappear because the updated=true filter is still applied.
- The remaining items where Updated=true will show.
- All items show.
Throughout this sequence the Item.index column is updated to reflect the order only of those items that are visible.
Reload the page and repeat the sequence but do not include the first row in those you change. You will see that, although the Item.index column is still sequential from 1, when you apply the isFirst filter no rows are visible because isFirst appears to be applied to the underlying, original Item.index and not the one that results from filtering (or, in my previous sample file, from sorting).
Whether this is logical and consistent or not (or whether I am completely misunderstanding!!) my question is: How do I step through a filtered/sorted repeater row by row if I can't use Item.index or isFirst to do it???
20181023 Persistent ItemIndex.rp (76.6 KB)