Posted 18 May 2023, 4:43 pm EST
Hi
We are using Wijmo for Angular, currently @grapecity/wijmo.all version 5.20213.824.
Due to our backend performance, we have implemented paging in our FlexGrid.
Currently based on monitoring scrollPositionChanged and if we reach the end we emit an event to load next page.
That works fine for us, and the solution has run like this in several years.
Now we are looking at implementing our first grid with Grouping of data.
We have a few challenges with this.
- Collapsing a group messes with our paging logic.
** E.g. our pagesize is 50 rows, if a group has 400 rows, we will need to page multiple times after collapsing to show next group - Groups first appear when data is loaded - so as you scroll more groups will appear.
** Combined with the above, it make it hard and clumsy to work with. - Sorting - we would like the groups to be sorted alphabetically - but still be able to sort the grid by something else.
So - my question is.
Are there any good/other way of implementing paging, that works if you have groups. (E.g. an direct event from Wijmo that end is reached - instead of using scrollbar as indicator)
Would it be possible to load groups first - and then on expand do LazyLoading - similar to lazy loading nodes in the TreeView?
Or is the only way forward here to ensure that our backend is optimized enough to load 100k+ rows, and rely on the grid being able to handle/render that many rows with groups?
I am just looking for hints on where to go - if we should spend time on getting paging to work - or just discard that when grouping is enabled - and go for full dataset at once.
Best regards
Anders
