Forum Discussion
Reordering Column Headers in Matrix with Field Parameters and Calculation Groups
- 5 months ago
Hi SamVH12
Althought the visibility is controlled by a field parameter, field parameters are essential just field selectors - they are not actual columns. Measures in matrix are currently always at the bottom of the hiearchy. A workaround is to materialize the results of these measures in a disconnected table containing the measure names using another measure and add that column together with the measure to the matrix visual.
Please see the attached pbix.
- Anonymous4 months ago
Hi SamVH12
Thank you for reaching out to the Microsoft Fabric Forum Community.
Thanks for the inputs danextian collinq
Inputs from users are very valuable, and additionally, based on my understanding, Power BI doesn’t fully support all of these requirements working together. If you keep both field parameters and calculation groups, everything stays flexible, users can pick measures and time options independently but the downside is that you can’t rearrange the column hierarchy. Measures will always show up at the lowest level in the matrix. If you switch to a disconnected table approach, you do get control over how the columns are displayed, which is nice. But then you lose the ability to have separate slicers for different measure groups, since everything gets combined into one selection. So it really comes down to a trade-off: you can either keep the flexibility with multiple slicers, or control the column layout but unfortunately, not both at the same time.
If there are any deviations from your expectation please let us know we are happy to address.
Thanks.
HI SamVH12 ,
I do not think that you can do your request with calculation groups and field parameters. Column hierarcy order is controlled by Power BI. So, the order cannot be chagned.
However, I looked it up and found this answer:
Keep calculation groups, but move slicer logic into display structure
Key idea
Do not fight the Matrix header order
Instead control what users pick before it reaches the Matrix
How it works
Keep:
FP1, FP2
CG1, CG2
But:
Disable column hierarchy
Show measures only at the lowest displayed level
Add custom column headers via dynamic titles or tooltip labels
🔹 Users still slice independently
🔹 Matrix still evaluates properly
🔹 Headers look cleaner, even if technically hierarchical
This is the most maintainable approach in large models.