Grouping in OData Table Widget
Stephane_Bouillon
Customer Advanced IT Monkey ✭✭✭
Hi,
I noticed that when I drag a column header of an OData Table Widget or a search results list to the grouping row it does so on a page by page basis instead of reordering the items and keeping all the grouped items together. This is not intuitive and also different of how the grouping feature used to work in previous releases of the portal.
Is this a bug or by design ?
Stephane
Best Answers
-
seth_coussens
Member Ninja IT Monkey ✭✭✭✭
@Stefan_Barrett this is actually an issue with the Kendo UI controls and graphs we are using when you attempt to do both server side and client side grouping. For performance reasons we do server side grouping, so the UI is only seeing the first X results and the rest are never returned from the server. When you search or page, it searches all the results and the page moves to the next set of results as expected.
In the UI though, when you group via the drag and drop method, it's a client side grouping, and so only groups the items the client sees (which in our case is the already paged and grouped set of results).
To resolve the confusion here we will be disabling the UI based grouping and the grouping will be determine in the configuration of the widget. (Really, this is how it works already)
Sorry for the confusion.
5 -
Michael_Aidinovich
Cireson Solution Architect Advanced IT Monkey ✭✭✭
@Stefan_Barrett wanted to follow-up to let you know that in SMP Baseline 9.4.5 the grid grouping was corrected. Feel free to download from https://softwaredownloads.cireson.com/#/ and give it a go.
5
Answers
Hi Stephane,
Good question. Running it by the Dev team and will let you know as soon as I have the answer.
Mike
Hi Stephane,
Haven’t forgotten about your question and wanted to let you know Cireson is looking into this. I'll post again once I know more.
Mike
@Stefan_Barrett this is actually an issue with the Kendo UI controls and graphs we are using when you attempt to do both server side and client side grouping. For performance reasons we do server side grouping, so the UI is only seeing the first X results and the rest are never returned from the server. When you search or page, it searches all the results and the page moves to the next set of results as expected.
In the UI though, when you group via the drag and drop method, it's a client side grouping, and so only groups the items the client sees (which in our case is the already paged and grouped set of results).
To resolve the confusion here we will be disabling the UI based grouping and the grouping will be determine in the configuration of the widget. (Really, this is how it works already)
Sorry for the confusion.
@Stefan_Barrett wanted to follow-up to let you know that in SMP Baseline 9.4.5 the grid grouping was corrected. Feel free to download from https://softwaredownloads.cireson.com/#/ and give it a go.