Pagination + Grouping. The UX is confusing.
If you are using pagination and grouping you will see that when expanding/collapsing the groups, the row count and potentially the number of pages change.
Also, you might find that the leaf rows for a group expand through many pages, making it difficult for the end user to know the parent group for the rows they are looking at the moment.
We are aware that these are not ideal for the UX experience, but at the same time we have no solution since combining grouping and pagination causes naturally an awkward UX experience
Note that most applications that use pagination avoid grouping and vice versa, we don't think there is any strong industry standard for combining these two features.
We keep an eye open and try to improve the coexistence of these two features, but at this time we have nothing in the pipeline.
If you think you know a better way of integrating grouping and pagination, please contact us with your suggestion.
Note that we have added this to the pipeline:
|AG-2762||Master/Detail + Pagination: Allow pagination to only count master rows as rows that count towards the page limit|
This might help when using master/detail