Seems table grouping is funky again...

If I have multiple levels of grouping, and set the last one as "row number", the system is NOT supposed to show a drill-down page for the row numbers... instead it's supposed to group by the previous grouping element.

6e1e5283-cd25-4354-aed1-17d4de70a4c6
You can learn more about multi-level grouping here

The behavior noted in the image above (from the docs) is not happening anymore; instead we're getting an additional drill-down page for the row number. (Which is not helpful).

eba9a06b-7175-4e40-9549-4d2c5d4f2257

In the gif above, I shouldn't see the # grouping - instead I should see a table of all the records for the J33 grouping.

-------------------------------------------------------------
For reference this method of controlling the grouping is a "special" case.
- The ultimate behavior we (the app users) were wanting was:
- Drill down, and on the last grouping, you see the records grouped by that grouping.

To make this happen, originally we could insert duplicate entries into the grouping options on the view; meaning if I wanted to see records grouped by the last grouping option... we would literally insert a duplicate of that option.

Group By: [Status]
                    [Status]

The fields in the view (where we select what column to use) were changed at some point a few years ago to NOT allow duplicates... this broke that behavior that us app users were depending on.

To make things work, they inserted a special case for the row number as the last option in the grouping.
- This special scenario has just broken.

4 6 180
6 REPLIES 6
Top Labels in this Space