In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:
Below table is an example from a fictional Position Planning application. The left column shows items of a dimension called Position. Issue is, some users might not recognize these items as Positions. I would like to be able to help them by adding a Dimension Header to the table, which currently isn't possible.
Some workarounds include using a line item with formula ITEM() as the first column, using a Top Level item to indicate what the list is or making one list item the header. All might work in a very simple table like this, but the more complicated the table, the worse it's going to look and the more difficult it will be to read. For example for a table like below none of the workarounds would make sense. Only acceptable solution here would be to have native Dimension Headers in the same line as the line item Column Header.
How often is this impacting your users?
Often - all customers have some tables where they would benefit from this.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
End users
What would your ideal solution be? How would it add value to your current experience?
A simple selection of whether the dimension header should be shown on hidden. Hidden would be the default selection.
Please include any images to help illustrate your experience.
