Sorting in groupby

[Rifad]

Greetings, community members!

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:

1. Low
2. Normal
3. High
4. Urgent

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.

[Suvrutt_Gurjar]

If understanding of your requirement is correct, I would assign the prorities in an enum column with order of options in enum column as 

Low

Normal 

High 

Urgent 

Then I would group the view by this enum column.

[Rifad]

Yes its setup like that.

[Rifad]

---

@Rifad wrote:

---

You can notice its Urgent, Normal, Low High but it should be Urgent, High, Normal, Low

[Suvrutt_Gurjar]

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 

Urgent

High

Normal 

Low

and then use that column as group by column.

[Joseph_Seddik]

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,

---

@Suvrutt_Gurjar wrote:

I would assign the prorities in an enum column with order of options in enum column

---

I believe our friend was talking about adding the values in the column definition, not the data source.

[Rifad]

@Suvrutt_Gurjar 

Did you mean like this ? I tried this and did not work.

[Rifad]

---

@Joseph_Seddik wrote:

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

---

Thanks @Joseph_Seddik for reply.

As per this it looks ok but is there any way other than this to avoid this numbering ?

[Joseph_Seddik]

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.

[Joseph_Seddik · Accepted solution]

High --> Quite Urgent, Urgent --> Top Urgent?

[Rifad]

I had to do something like this to avoid numbering for now considering no other options. Thanks @Joseph_Seddik & @Suvrutt_Gurjar 

[Marc_Dillon]

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.

[Rifad]

Yes you are right. I checked and it did not work. I thought its an intended behaviour.

[Suvrutt_Gurjar]

Hi @Rifad ,

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

Categories view included as a view in dashboard view:

Categories table:

Products Table:

With Category table as reference.

Category table:

[Rifad]

Thanks @Suvrutt_Gurjar

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.

[Suvrutt_Gurjar]

You are welcome.

[Rifad]

Here comes another challenge. This is sorting as per status ref key not as per the label. How do I fix this ?