I’ve just started experimenting with the Data Grid Visualization. If I sort by a column and then group by that column, the data grid ignores my chosen sort order and sorts the groups in an unexpected, seemingly random order. I would expect the group by to sort ascending by default and allow also descending.
Great work.
Hello @Howard_Jacobson,
Thank you for your message. We have created an internal ticket to implement the sorting of grouped data. We will notify you as soon as it is done.
Regards
Nazar
Thanks. This will be very helpful.
Hi,
Is there an update on the intended Data Grid Visualization feature of being able to sort grouped data? The groups still come up in a random order after grouping.
Also, I noticed that the Filter icon offers a dropdown list that has all the fields/properties from the source data table, yet all the fields may not be available for viewing (depending on the data grid configuration). Shouldn’t the selectable columns for filtering be the same as those offered in the Group By dropdown list, that is, only the columns visible in the Data Grid? The app user might get confused about an option to filter unseen data.
I am trying to pre-sort a data table on two fields before it goes into the data grid. My logic is not working. The first level sort is desired to be on a text string field. The second level sort should be on a timestamp. Must the timestamp be converted to an Unix integer first before sorting?
My logic behind the Data Grid Visualization component is an “On Before Mount” handler with a Print block then a “Load Grouped Table/View Objects” block with the timestamp column name tied to the “sort by” property and the text string field name tied to the “group by” property. The objects in the data grid do not follow this specified component logic. The data grid ascending and descending sort function for each column is responsive, but this works only for one column at a time. What corrections do I need to make for a two-level sort in a data grid?
Hello @Richard_Elieff
Currently, visualization tasks are not a high priority. However, we can bring this up with the team to discuss potentially increasing its priority. Could you please let us know how critical this issue is for you?
Kind regards,
Viktor
Hello Viktor,
I found a workaround for the issue, so it is not critical anymore. Instead of using a visualization data grid, I will use a data table (read only, so without editing capability). The user can first filter on the text string field, which is a name, to isolate a single common group of records. The user can then sort on the timestamp column for that filtered group. This approach is less efficient than seeing the whole table of records grouped by name then sorted by datetime. However, it still works.
My additional suggestion now is for adding a little more embedded functionality into the Data Table component. Specifically, a simplified aggregation feature as well as the ability to change column widths would be nice.
Regards,
Richard
Hello, @Richard_Elieff
Thank you for sharing both the workaround and your ideas for the Data Table. We will discuss these with the team, and your feedback will be taken into account as we plan future improvements. It is much appreciated.
Kind regards,
Karyna
Hi Karyna,
I noticed that the Data Table component already offers the column width adjustment feature. It is in the column configuration window under the name box. I previously overlooked (or forgot about) it; sorry about the unnecessary request. So, column width is not an improvement your team needs to consider since it is already available.
Regards,
Richard