I would like that each group's items list is loaded on demand when the user clicks the group.
The purpose is not to load all data from the server but rather only when the user hits the requested group.
Does the Grid support this functionality?
6 Answers, 1 is accepted
The Grid does not support loading the groups on demand. One possible way to implement this behavior is to bind the Grid to the group keys and use a detail to load the items for the group on demand.Regards,
the Telerik team
Binding to the group keys and load their items on demand sound reasonable.
However, Can I make the details pane look the same as a group pane?
The nice thing about grouping is that the group and its items share the same column structure. When using detail pane is that possible?
The same structure cannot be used because the detail is added in a cell of the Grid and the group rows are part of the Grid table. You could achieve similar look by using some templates and adjusting the styles. For convenience, I attached a sample project.Regards,
the Telerik team
Do you have a solution now for this problem? I mean, other then the prior suggestion. Do you plan to implement this functionality? It's very frustrating to apply hacks instead of using a proper implementation of server grouping.
I have noticed that this thread is a duplicate of a private Support thread of yours. I am pasting below the response provided there:The Grouping functionality of the Kendo UI Grid could be executed on the client-side and on the server-side. However, either of the cases, the respective items would be loaded even if the groups are collapsed. The server returns the grouped data and grouped data could not be loaded on demand. The hierarchical data could be loaded on demand.
The groups that are shown in the grid's content are actually simple HTML elements which are separators for the groups and indicate where one group starts and ends.
As an alternative, if you have a hierarchical data, I would recommend utilizing the Kendo UI TreeList widget which provides loading of its child elements on demand. An example could be found here:
It is recommended to avoid submitting duplicate tickets as this might end up polluting your history. Therefore, it would be more difficult for you to navigate through past tickets.