Forum Discussion
Dynamic “crosstab” in Power BI: multi-level dimensions + dynamic measures
I’m working on a self-service “crosstab” matrix in Power BI that must behave like a Tableau pivot table, and I’d love to crowdsource ideas for a cleaner approach.
Users need to pick up to 6 different row dimensions via slicer.
Users also pick one or more measures via slicer.
The matrix should render all selected dimensions as hierarchical column fields, and all selected measures as rows, with no extra clicks.
No drill-down icons (±), no bookmarks or toggling of separate visuals—just one matrix that auto-expands every level and updates immediately when slicers change.
What I’ve tried
Field parameters for fields + metrics
✔️Dynamic selection via slicers
❌Doesn’t auto-expand — users must click the expand icon each time
Bookmarks + dual-matrix (“ResetView” / “ExpandedView”)
✔️Pre-expanded states
❌Requires manual bookmark click whenever slicers change
Flattened approach with 6 calculated columns (Level1…Level6) and unpivoted metrics
✔️Always-expanded, one matrix
❌Complex DAX and maintenance overhead
Where I’m stuck
I can get each technique to “almost” work, but none meet all requirements simultaneously. Every approach forces either user clicks, multiple visuals/bookmarks, or huge maintenance overhead.
What I’d love to learn from you:
Are there any alternate patterns or new features (maybe in Fabric / Calculation Groups, or upcoming matrix enhancements) that let me:
Dynamically pick N row fields via slicer
Dynamically pick M measures via slicer
Render them in a single, fully expanded matrix
Without manual drill or bookmarks
Has anyone built something similar in Power BI or in Fabric that I could reference?
Attached screenshots for reference:
Post hitting the drill down option:
Thanks and Regards
Hi Buddyy1512,
Thank you for reaching out to the Microsoft Fabric Forum Community.
The exact Tableau style pivot experience, such as auto-generated and auto-expanded hierarchy, can be done in Tableau but cannot be achieved in Power BI.
If this is a key requirement for your reporting needs, I strongly encourage you to submit this idea to the official Microsoft Fabric Ideas portal. If you get enough votes, they may consider it in the future.
Fabric Ideas - Microsoft Fabric Community
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
4 Replies
Hi Buddyy1512,
Thank you for reaching out to the Microsoft Fabric Forum Community.
The exact Tableau style pivot experience, such as auto-generated and auto-expanded hierarchy, can be done in Tableau but cannot be achieved in Power BI.
If this is a key requirement for your reporting needs, I strongly encourage you to submit this idea to the official Microsoft Fabric Ideas portal. If you get enough votes, they may consider it in the future.
Fabric Ideas - Microsoft Fabric Community
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
Thank you for the prompt clarification and for highlighting the current limitations in replicating Tableau-style pivot experiences in Power BI. I appreciate the suggestion to submit this as an idea on the Microsoft Fabric Ideas portal—I'll certainly consider doing that.
Thanks again for your support. I’ve marked your response as the solution to help others who might have a similar query.
Thank you for the prompt clarification and for highlighting the current limitations in replicating Tableau-style pivot experiences in Power BI. I appreciate the suggestion to submit this as an idea on the Microsoft Fabric Ideas portal—I'll certainly consider doing that.
Thanks again for your support. I’ve marked your response as the solution to help others who might have a similar query.
The Field Parameters approach is the right direction for this use case. For up to 6 dynamic row dimensions, stack multiple Field Parameters in the Rows well of the Matrix each one controlled by its own slicer. For dynamic measures, a separate Field Parameter in the Values well.
Known limitations you'll hit with this approach:
- Sorting breaks when combining static + dynamic fields in the same well
- You can't control column order dynamically (measures always appear in the order defined in the Field Parameter)
- Cross-filtering between two Field Parameter slicers doesn't work as expected
For a Tableau-style self-service experience where end-users pick dimensions AND measures AND reorder columns themselves in the published report without going back to Desktop Flexa Tables on AppSource handles this more cleanly than the Field Parameter workaround. Users drag dimensions and measures into the visual directly in Power BI Service
