Hi All,
I have a query that "Do we have any limit on number of rows to display in an editable grid?".
I have a requirement where I am fetching the data from DB and showing in editable grid for user to edit and update but after few months it might be possible that the number reaches to 10k.
So just wanted to know if we have the limit of rows in editable grid.
Discussion posts and replies are publicly visible
There is no hard limit, but the performance will suffer very hard as you try to display hundreds of rows.
You will have to find a different approach. Maybe this: https://docs.appian.com/suite/help/23.4/recipe-use-links-in-a-grid-to-show-more-details-and-edit-data.html
Or you can add paging to your editable grid like shown here - appianspace.com/.../
Or: https://appian.rocks/2023/07/24/universal-paging/
Thanks Stefan and Harshit for your response.
I have already the approach to use custom paging in editable grid but due to custom paging I am unable to achieve few other things.
1. When I use checkbox selection it holds data for all the selection but when I select and unselect then issue comes like it not saving the ids correctly.
2. When I use Remove icon in each rows and click on it then also not working as sometime it removes one row but sometime whole data from the grid.
But when I remove paging then all works good but in future number of rows limit might create issue so raised the concern.
User want to select multiple items in Grid and then update those rows in DB on different pages.
this link https://docs.appian.com/suite/help/23.4/recipe-use-links-in-a-grid-to-show-more-details-and-edit-data.html is helpful when user select only row for editing but there they want to edit 200-400 rows in one select by just checking all values are correct or not.
That use case you describe is not a good fit for Appian. I really suggest to discuss this requirement. You know, once Excel is the only tool you have, everything looks like spreadsheets.
https://theconversation.com/spreadsheet-errors-can-have-disastrous-consequences-yet-we-keep-making-the-same-mistakes-219356
Yes Sure will discuss with users about this but meanwhile we are trying to reduce the data by applying multiple default filters.
Please please please don't do this. For data sets beyond a dozen or so items, use a filterable paging grid where each row can (individually) be clicked on to open a separated editor, where the user makes, validates, and saves any changes independently before moving onto other edits. Editable grids that try to do 1000 different things to 1000 different rows are the bane of user experience (and impossible to maintain, unless kept exceedingly simple).