Grouping - Added Option of Non-Aggregation

When using grouping on a multiple selection column, I don’t always want a group of the multiple selections; I’d rather have each individual selection within the multiple selection be duplicated in each individual selection.

EX:

Selectable Options to be Grouped: A, B, C, D

Table item selected: A, D

Current display groups: A , B, C, D, [A,D]
and the table item is only listed under [A,D]

Wanted display groups: A, B, C, D
wanted table item to be displayed in the A group and also the D group; with no [A, D] group

Use case:

There are different groups of student attending an event that covers multiple days, and within each date are separate classes for different groups of students.

I want to have at the left a DAY group and a TIME group that list the class, and that class would only to apply to multiple groups of students. I want the student groups to be grouped across the top of the table. If more than one student group is called to a single class, I’d like that class to be listed once under each individual student grouping and NOT an additional column group of the collection of applicable student groups.

@Artistic_Director ,
I have had the same problem with my travel-planning, having participants enroll themselves into more than one trip.
There are two different situations, solved in more or less the same way: data received by people submitting a coda form, or existing rows being edited in a table or modal.
In my situation I used an automation (triggered by form submitted or by row changed) in which I count the number items in the multiselect field and, if greater than 1, duplicate the row that many times. In each new row you place just one of the multi select items. When done, you delete the original row (Step 1 Result).
From here on, your grouping is working the way you want.
Depending on what your data looks like, you might have to do some fine tuning: as in any database, you don’t want to much data to repeat over all your rows. So ideally, the only thing repeating is the name of the student and not their age, grades, addresses, etc. All of these issues can be solved (which is not too complicated, but some effort is required), but elaborating about that is for another topic.
Greetings,
Joost

Hey, is the below the output that you’re hoping to achieve?

If not are you able to send a little demo / manual mock up of the table output desired.

Thanks,

Chris