starred/radzen-blazor
1
0
Fork 0
mirror of https://github.com/radzenhq/radzen-blazor.git synced 2026-02-03 21:29:20 +00:00
Code Issues 1.3k Packages Projects Releases 22 Wiki Activity

Feature Request: Optimized rendering for initially collapsed groups in data grid. #421

New Issue
Closed
opened 2026-01-29 17:37:01 +00:00 by claunia · 1 comment
claunia commented 2026-01-29 17:37:01 +00:00
Owner
Copy Link

Originally created by @OndrejUzovic on GitHub (May 24, 2022).

Currently, in case of grouping the data grid rendering runs in two iterations:

  1. All lines are rendered and displayed without grouping.
  2. Data grid re-renders and displays lines with expanded or collapsed groups.

(As also visible in the demo: https://blazor.radzen.com/datagrid-grouping-api)

Now, if I understand correctly, the grouping does not work together with the virtualization. And using the grouping together with the paging is restricted only to the active page (which is not very practical if data goes across multiple pages).

So in case the data contains several thousands of items the rendering of all lines causes a significant performance degradation.

However, in many scenarios the performance could be improved if there is a possibility to specify a group shall be initially collapsed and the data grid would render it collapsed in one iteration.

Would it be possible to consider such improvement? Or do you have some other plans for this issue?

Originally created by @OndrejUzovic on GitHub (May 24, 2022). Currently, in case of grouping the data grid rendering runs in two iterations: 1. All lines are rendered and displayed without grouping. 2. Data grid re-renders and displays lines with expanded or collapsed groups. (As also visible in the demo: [https://blazor.radzen.com/datagrid-grouping-api](https://blazor.radzen.com/datagrid-grouping-api)) Now, if I understand correctly, the grouping does not work together with the virtualization. And using the grouping together with the paging is restricted only to the active page (which is not very practical if data goes across multiple pages). So in case the data contains several thousands of items the rendering of all lines causes a significant performance degradation. However, in many scenarios the performance could be improved if there is a possibility to specify a group shall be initially collapsed and the data grid would render it collapsed in one iteration. Would it be possible to consider such improvement? Or do you have some other plans for this issue?
claunia commented 2026-01-29 17:37:02 +00:00
Author
Owner
Copy Link

@akorchev commented on GitHub (Feb 21, 2023):

There is now a property which displays all groups collapsed by default. Demonstrated in the grouping API demo.

@akorchev commented on GitHub (Feb 21, 2023): There is now a property which displays all groups collapsed by default. Demonstrated in the [grouping API demo](https://blazor.radzen.com/datagrid-grouping-api).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#421
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?