I am seeking assistance on a matter regarding the possibility of implementing an alternative sorting mechanism for the “groupby” operation. Specifically, I am interested in arranging the grouped data based on their respective priority levels, as follows:
I attempted to approach the task from a distinct perspective, employing numerical representation, but the result appears aesthetically unappealing. I kindly request any recommendations or suggestions for improvement in order to enhance its overall presentation. Thank you in advance for your valuable input.
Yes, I got it. So to group it in the desired order, the column having category option , I would set the enum options in the column settings in the order
It’s a common business practice to assign numbers for priorities; to avoid confusion and misconceived interpretations. For example, I wouldn’t know for certain, which of “Urgent” and “High” has the highest priority. So, I would name them like:
Priority 0 - Top Urgent
Priority 1 - High
Priority 2 - Normal
Priority 3 - Low
Or something like it. Here, you wouldn’t miss on aesthetics and you would also give your users clear indications about what task has a higher priority than another.
Also,
I believe our friend was talking about adding the values in the column definition, not the data source.
Other than @Suvrutt_Gurjar 's suggestion, none that I know of. I’m sorry.
But really, we already have sorting options to set, so it is useless to be forced to set a sort based on the grouping should we define one. Sorting and grouping should be two separate settings.
FYI, enum option sorting order does not work when using Ref values to another table. I had a support ticket submitted on this a long time ago, before the support switchover. Aleksi had even responded agreeing that it should work in that case and saying that they were working on it. But nothing ever came of it.
Sorry for reverting a bit late on this. I was testing some alternatives. As Marc rightly guided, I realized after posting that the enum proposal may not work in this case. Very sorry about my bad. I typically post such critical suggestions after testing. In this rare case, I missed it.
The following approach may or may not be useful to you because your requirement could be still very specific. But it could help someone else looking for a similar implementation.
The example below has Products table with products being accorded a priority from a 4 rows Categories table as a referenced or parent table. So the various product records become children records of the Category table.
Then one could display the Category table with summary view as Card type view. The Card view allows related children records ( Products records in this case) to be displayed in place of image placeholder. So the below collection or summary view displays the related Product records in the desired order of Urgent, High, Normal and Low
Categories summary card type view:
This view is sorted by ID of the Category table in ascending order. So it displays in the order Urgent, High, Normal, Low
splitting into different sections won’t be a good idea for me currently. I have multiple dashboards like purchase, jobs, quote, sales I mean the entire app modules utilising single table for comments like screenshots i shared above. In this scenario management of these is literally x4 that is not practical. If it was for just one dashboard this works.
Thanks as always for providing me your valuable informations.
