In a Table View, setting a 'Group by' column removes column from the "grid". Explicity setting it into Column Order should override that

[Marc_Dillon]

As seen in the screenshot, I’ve set the [text] column as the ‘Group by’ column. Default behavior in this case is that this column does not get displayed in the table grid, but instead shows as a header for a set of rows.

My request is that under the above circumstance, if you also explicitly add that column into the ‘Column order’ section, then the column should again, and redundantly, appear in the table grid.

[Lynn]

I think you used to be able to do that. I would vote but I dont have any left.

[Marc_Dillon]

I’m still wanting this. I assume this would also fix the missing column headers brought about by using LINKTOFILTEREDVIEW().

[Marc_Dillon]

I ran into another situation today where I’d like this functionality.

[1minManager]

Just out of interest, whats the rational behind this?

[Marc_Dillon]

Once the user navigates into the “sub-view” (for lack of better term), whether this is from a multi-level Group-by or a LINKTOFILTEREDVIEW, the column that was filtered/grouped by is now impossible to show in the “sub-view”.

[1minManager]

O I C

The only way I can think to hack this would be to have two columns with the same data. One for the grouping and the other the colun in the sub-view

[Marc_Dillon]

1minManager:

The only way I can think to hack this would be to have two columns with the same data. One for the grouping and the other the colun in the sub-view

Yep, same.

[Austin]

I feel like since a virtual column that just copies the data doesn’t add a ton of complexity or time, that there is basically no hope for this feature?

[Marc_Dillon]

Wanting this again today.

[Marc_Dillon]

Wow it was only last week that I last bumped this? Sigh...