Description
Requirements –
- Manage pagination at each group level.
- Load group on demand when user clicks on row expand.
https://i.pinimg.com/originals/81/ad/be/81adbef7d4758b011ad43b2315164395.png
https://i.pinimg.com/originals/31/92/52/31925269ceafbcaecdef762c3ee2ef2d.png
The ui grid displays columns : Severity, Name, Status, caseID, AssetID, AssetName, SiteName ....soon total 12 columns.
Issue –
-
Apply Grouping on Severity, Status, AssetId, caseId columns.
-
By default grid displays Severity group as level zero.
https://i.pinimg.com/564x/a5/aa/f3/a5aaf37583f059702615cfbb62dca7ff.jpg -
When we expand Severity “One” entity, application request API to fetch top 100 distinct status where severity is equal to one.
https://i.pinimg.com/564x/fa/1d/23/fa1d2324b2af45b4195426a99a5310cd.jpg -
On expand of Closed status entity the application request API to fetch top 100 distinct AssetId list where status is equal to closed and severity id equal to one
https://i.pinimg.com/564x/b8/8b/23/b88b23ed00029f5a4785a68eae083c3a.jpg -
At this level we can observe some empty rows i.e. null value rows are created. The application refined dataset correctly.
-
Issue Root Cause Guess – as the source data set which is injected to ui-grid is refined correctly based on the grouping conditions & API response the UI-Grid visibleRowCatche is not updated when compared with bonded dataset