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
Discussion posts and replies are publicly visible
Without more details this is so hard to tell. I think the error message is obvious. If you can shore more, we might come up with ideas what the root cause could be.
Unfortunately, this is all the information we have. Additional info is we are using the following query in a dashboard where we show 10 tasks per page in a read only grid. The user can select on those tasks and will assign to themselves and start working on those tasks.Page size is 10 and paginginfo for the query has been configured as fv!paginginfo.
hi Sarathkumar R could you post your code snippet please that would be better idea
a!queryProcessAnalytics( report: cons!REPORT_NAME, query: a!query( logicalExpression: a!queryLogicalExpression( operator: "AND", filters: { a!queryFilter( field: "c14", operator: "<>", value: loggedInUser(), applyWhen: ri!taskAssignement = cons!NAME[2] ), a!queryFilter( field: "c17", operator: "in", value: ri!PM_ID ), }, logicalExpressions: { a!queryLogicalExpression( operator: "OR", filters: { a!queryFilter( field: "c4", operator: "=", value: ri!search ) }, ignoreFiltersWithEmptyValues: true ), a!queryLogicalExpression( operator: "OR", filters: { a!queryFilter( field: "c22", operator: "=", value: loggedInUser(), applyWhen: ri!taskAssignement = cons!NAME[2] ), }, ignoreFiltersWithEmptyValues: true() ) }, ignoreFiltersWithEmptyValues: true ), pagingInfo: ri!pagingInfo ) )
This is the query we are using in the read only grid. We are calling this query in the data parameter of the readonly grid and for ri!paging info, we are passing fv!paginginfo as the value.
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