Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hi all, This is driving me crazy. I have a simple sum calculation that I'm putting in a matrix visual with a fiscal year and month to slice it. When it put the Fiscal year and month on rows, I get the correct calculation. When I switch it to columns, it gets crazy pants as shown below.
Measure is
Fiscal year is offset by 3 months and the month field is sorted by the alternate sort
fact table is just random values with a period key
What is even going on?
Solved! Go to Solution.
Alrighty, based on @bchager 's first response, It occurred to me that the first month was actually displaying the subtotal and labeling it as a category. I went in the Format visuals pane and turned the Column subtotals on and then off again. It's working fine now. Going to raise a ticket with MS since this is definitely a replicable bug.
Thanks so much!
Alrighty, based on @bchager 's first response, It occurred to me that the first month was actually displaying the subtotal and labeling it as a category. I went in the Format visuals pane and turned the Column subtotals on and then off again. It's working fine now. Going to raise a ticket with MS since this is definitely a replicable bug.
Thanks so much!
I see what the 31,894 is composed of after bringing in the PeriodKey field. Could it be because you don't have any date fields in your matrix?
It's a thought but without a date field, shouldn't they act as categories anyway? Why would it add data that isnt actually on the periodkey in the slot of October?
On a lark I modded the initial model with additions to the date table with the sort reinstated as so:
And ended up categorically with the same result.
What could be causing this behavior?
I'm not sure. I also noticed a disconnect between the PeriodKey in both tables. One of them has a 109 and one only goes up to 108. I'm spitballing here but is that a referential integrity issue?
Most appreciated, but in the larger model that this initially showed up in, there's no referential integrity issues. I'll test it here though.
No it isn't that easy. I just fixed it in the model and it stays the same 😞
I've read about issues some users are having with visualizations with the December 2023 release. Have you tried using a third party matrix from the marketplace to see if it behaves the same or differently?
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 103 | |
| 81 | |
| 65 | |
| 50 | |
| 45 |