Getting StartIndex must not be greater than TotalCount issue

Question

Hi All, 
 We are getting the following error as startindex cannot be greater than totalCount. Start index was 31 and totalcount was 0. We are using process report query for querying the data and for paginginfo, we are using fv!paginginfo. We are getting the above error only in prod and we are being notified via the error mail as part of the new appian release. No user has reported this issue. We are not able to understand why this error is occuring. One observation was when errors are triggered, startindex is having 11, 21,31,51 etc. Any suggestions will be helpful

Chris · Answer

We see this error regularly when filters are changed which reduces the data set size, after paging has been used. For instance, if you have a grid with paging set to 10 rows: 
 - Current filters return 30 items total, grid shows 1-10 - The user pages to items 11-20 - The user changes filters, which reduces the result set to 8 items - An error occurs because paging startIndex remains at 11, but there are only 8 items in the new data set 
 In that situation, any time the data set can be reduced by filters/etc, the resolution is to manually reset paging startIndex to 1 when any filters are by utilizing a!save(). 
 Appian

Mike Schmitt · Answer

Sarathkumar R said: Do we have to build paging icons separately 
 That's not what "manage the paging with a local variable" means at all. 
 It just means declare a local variable prior to the query i.e. "local!pagingInfo: a!pagingInfo(1, 10),", which is then fed into the query instead of fv!pagingInfo (in such cases I prefer to query in a separate local variable from the grid itself but I believe either way should work); then anytime the user-controllable filtering is changed, save "1" back into local!pagingInfo.startIndex.

Getting StartIndex must not be greater than TotalCount issue

Top Replies