After refresh of a section containing a paginated grid, the pagination state will be reset. That is an expected behavior.

Is there any specific reason why the section needs to be reloaded. Can we modularize this? If possible can we can reload only the section that does not contain this grid.

Hi,

This is a expected behavior from the product, however could you please elaborate on your requirement so that we can think of any alternative changes to achieve the functionality.

Thank you for all the responses. Below is the requirement:

1. Load the grid with result set of a query. The grid is on section X and the section is on a Local Action Y.

2. Select one of the values from the grid using a radio button from the second page using pagination. Here even though we select the radio button, the value is getting posted to the page only if the section is refreshed or use the OOO flow action submit. I have tried post value, refresh list which did not work.

3. Using custom FA buttons read the selected values which was chosen using the radio button. This implementation has the limitations -

A. In the events, upon clicking the button  I used a section refresh to read the selected value as without section refresh, the value is not posted on the page.

B. When I use section refresh, the page reloads to the first page, and not the second page from where I selected the value. I would like to remain on the second page itself as my selection is on the second page.

Thanks,

Remya

@RemyaPeethambaran

You can avoid page reset to the first page, firstly remove section - refresh. Retain post value in Action set of say Property A.

In Table configurations > General tab, Configure Row Refresh > Condition as "Property A Changes"

This will ensure that only the row is refreshed with the value that you've posted and the focus remains on the same page.