Refresh ReadOnly Grid

RE: Refresh ReadOnly Grid

daisyMSingh — Thu, 20 Feb 2025 09:03:42 GMT

Pagination can be created to handle such scenarios .Normally we do to navigate to and back in editable ones.Better To create Ones in case of issues to have more Control over the batchsize ,movements and refreshes.
Just make
refreshAfter: "RECORD_ACTION",
refreshAlways: true()
if you are playing with Records It will Help more on that.

RE: Refresh ReadOnly Grid

Mike Schmitt — Wed, 19 Feb 2025 13:38:46 GMT

[quote userid="234820" url="~/discussions/f/user-interface/38545/refresh-readonly-grid/145456"]performing internal sanity checks instead of resetting the index[/quote]

TBF there used to be zero checks, the only result was an error. Then they added sanity checks, and the result of said sanity check was resetting the start index. I agree that with some effort, this could be made a bit more situationally observant - however your choice now is between waiting 2 - 10 years for Appian to implement this, to stay "low code", or to implement it yourself, to get the functionality you want.

RE: Refresh ReadOnly Grid

Stefan Helzle — Wed, 19 Feb 2025 07:33:12 GMT

You could manage the refresh and paging yourself and disable the automatic refresh as the user navigates to a page > 1.

RE: Refresh ReadOnly Grid

Saahil Mulla — Wed, 19 Feb 2025 04:06:23 GMT

Thanks for your prompt response. I appreciate your insight. Although I can implement that code, it may compromise our low-code standards. I believe Appian could enhance the user experience by performing internal sanity checks instead of resetting the index. This would greatly improve the overall user experience.

RE: Refresh ReadOnly Grid

Mike Schmitt — Tue, 18 Feb 2025 16:28:36 GMT

I believe (but haven't tested) that this internal refresh behavior is intentional and, to some extent, required. Say you're viewing (and auto-refreshing) a highly variable data set (which Appian has to assume is possible, as it has no way of knowing either way), where at any given minute, the grid could have 3 pages or it could have 10 pages. If you've navigated to page 8 of the data, and the auto refresh occurs, and now there are fewer than 8 pages' worth of data - if your paging info still has you viewing page 8, the grid will throw an unfriendly-looking error. Instead, Appian presumably ensures that all auto-refreshes will be "sanitized" for this behavior by resetting the (internal) Start Index back to 1 for each refresh.

You can probably work around this by querying your data externally (and storing your paging info externally as well), and refreshing your data that way. You'd just need to make sure to check that the data size after any given refresh is compatible with the old Start Index (i.e. the data is long enough that the start index will still make sense, lest it throw an error), and otherwise, reset the start index (which i think is doable, as long as you're reasonably versed in writing this code manually).

RE: Refresh ReadOnly Grid

nassera30 — Tue, 18 Feb 2025 12:18:24 GMT

I will try to answer without seeing your code, I believe when you set a refreshInterval on a read-only grid it refreshes the entire grid and this includes the fv!pagingInfo. So every time the grid refreshes, in your case, every 30 seconds, it resets the pagingInfo to the default page (1-10), which is why you are seeing the navigation reset.

I think it’s best you maintain the selected page manually using a local variable for pagingInfo, so that even after refresh, the grid retains the current page.