195603 - no subject - Hi All,\n\nI have created a report with

You should reset your pagingInfo variable as part of the saveInto attribute of all your filter fields: a!save(local!pagingInfo, topaginginfo(1,20))

Hi Sailesh,
Along with the solution as mentioned by Tim, few related post links in the forum are as given below :
forum.appian.com/.../e-106402
forum.appian.com/.../e-105983

Hi Tim,

I tried as per the solution mentioned above, but if I use a!save(local!pagingInfo, topaginginfo(1,20)) then I am not able to move forward with other rows in thegrid beyond first 20. As hown in the attached image

Hi Sailesh,
If you could share your SAIL code and related rules or else try with the solution as mentioned by Giridhan for resetting the paging info in the link below :
forum.appian.com/.../e-135904

@saileshd I would like to suggest you to attach the code snippet. Doing so helps the practitioners to resolve the issue much faster.

To the best of my knowledge, a simple pagination reset as mentioned by @Tim Clarke should resolve the error issue you have experienced earlier.

Additionally check what your interface is doing when you try to paginate. That is, check if the interface refreshes the datasubset by fetching a new set of data when the user tries to paginate the grid. Technically speaking, load the datasubset with the new paginginfo and existing data(if the entire dataset is already queried and stored in the variable) or load the datasubset with a fresh query and the new paginginfo as an argument to the query. The new paginginfo is nothing but the value you have been using for the paging grid and should be available as save!value or paginginfo variable post saving. And this refresh could be made in 'saveInto' of paging grid component or with().

So I opine that the latest issue (that is, unable to move forward beyond 20 rows) might not be related to reset of the paging info as mentioned above.

Afaik, it's related to application of the updated paginginfo against the already queried or to be queried dataset.

Hi Sonalk and Sikhivahans, thanks for your inputs, but I am still not able to understand the entire pagination concept. Attached is the code snippet of my interface for the report.

Code Snippet for a Report.txt

@saileshd Would you be able to test the attached code snippet and do let us know if it works?

In-case if the attached code snippet doesn't work, would you be able to attach the definitions of rule!ICAMS_createLogicalExpressionForInventoryAging() and rule!ICAMS_getModulesForInventoryAgingReport()?

Also please do let us know what you would like to know about pagination concept in general or after going through the attached code snippet.

You should put the update of local!pagingInfo in the saveInto of your filter fields not your gridField i.e. the radio and dropdown components

When you choose a value in one of your filter fields the expression will re-evaluate and your datasubset query will execute using local!pagingInfo hence why it needs resetting.

Great that works. Thanks everyone for the help. Thanks Tim for the explanation too! :)