Forum Discussion
dynamic subtitle for all measures without table name?
Hi Anonymous
You're getting a result that includes the table name because you're referencing the actual parameter field column – which contains the full field name including the table. This column is meant to act as a binding reference, not something intended for display.
However, there's also a limitation: you can't directly return the parameter field's name without the table prefix.
The common workaround is to add another column in the parameter table that stores a display-friendly label (e.g., just the measure name), and use that column for your dynamic title.
That’s what I did in my setup (see screenshots). I created an extra column (e.g., [category parametr]) that holds the readable names, and used that in the CONCATENATEX for the subtitle, instead of the parameter field column itself.
For example To get matrix as mine :At the first step add the column to parametrs table:
Then use it in the wanted DAX, like :
Title for parametrs = CONCATENATEX(VALUES('Categories for comparison'[category parametr]),'Categories for comparison'[category parametr],">>") & " sales analysis"Note:
The order of measures shown in the subtitle follows the sort order defined in the parameter table, which doesn't necessarily reflect the user's selection orderThe pbix with the example is attachedIf this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Super UserRitaf1983 you can simplify your approach by using Value4.
Note that I set the sort order to 0 but despite that it is now sorting alphabetically. You can no longer pivot by product then employee. It will always force the employee before the product. That is very, very different from prior behavior, and very annoying.
Super UserThanks for the suggestion. While less code can look more elegant, it’s not always simpler — especially when you need to explain the logic clearly to others. There’s value in building a multi-step solution that’s easy to maintain and understand.
From a UX standpoint, your approach also raises some concerns: when the slicer shows full table references and the dynamic title shows shortened labels, it creates a mismatch in language. That inconsistency can confuse users or make them question whether the fields are really aligned.
Also, giving up on the custom sort order might look minor, but it’s actually a UX decision too. Sometimes the order in the slicer is intentional — used to suggest importance or flow — and losing that hint can affect how people read the report.
(And as a side note: while I used the “>” symbol as well, it might be clearer to use commas in the dynamic title, to avoid suggesting an unintended hierarchy.)