Forum Discussion
Same measure in the same table visual giving different result
Hi ErikWarming ,
Based on my understanding and further testing, this issue can be fully reproduced in a minimal PBIX where multiple identical measures are added to the same table visual and one of them consistently returns an incorrect result based on column position. The same measures evaluate correctly in cards, matrices, and separate visuals, confirming that the DAX logic and data model are not at fault.
This strongly indicates a table visual evaluation/caching issue in the Power BI/Fabric engine. As a verified workaround, using a single measure with variables, a calculation group, or a disconnected helper table consistently resolves the problem. I’ve attached a simplified PBIX demonstrating both the issue and the workaround. Given the deterministic repro and resolution, this should be treated as a product bug rather than a modeling or DAX issue.
Thank you,Tejaswi.
Super UserErikWarming Hey,
- Dynamic format strings/calculation groups left “ghost” formatting on measures in the model. This can corrupt measure bindings in visuals (seen as the 6th column consistently mis-evaluating).
- It’s a model/engine bug seen with calc groups + dynamic formatting on SSAS 1500; persists even after you delete the calc group unless you clear the format string definitions and redeploy.
Quick diagnostics
- In DAX Studio, run a direct query against the model (not Power BI visual):
EVALUATE
SUMMARIZECOLUMNS(
'Date'[Year], 'Dim'[OmsGruppe],
"RealiseretYTD",[Realiseret YTD],
"BudgetYTD",[Budget Gruppe YTD],
"Diff",[Realiseret YTD] - [Budget Gruppe YTD]
)
If the numbers are correct here, it’s a Desktop visual bug; if wrong, it’s the model.
- Check measures in Tabular Editor: select all measures → ensure FormatStringDefinition is null (no expression). If any show an Fx icon, clear it.
- Inspect the table visual: remove all conditional formatting (icons/data bars), tooltips, and totals; test again. The 6th column symptom often stems from conditional formatting referencing SELECTEDMEASURE.
Fixes/workarounds
- Hard reset dynamic formatting:
- In Tabular Editor: for m in Model.AllMeasures → m.FormatStringDefinition = null; m.FormatString = "General" (or appropriate); save, deploy, process.
- Delete the old calc group, save, then restart SSAS (or recycle) and reprocess the database to clear cached metadata.
- Recreate base measures (new GUIDs):
- Create [Realiseret YTD v2] and [Budget Gruppe YTD v2] with identical logic.
- Create Diff using VARs:
Diff =
VAR r = COALESCE([Realiseret YTD v2], 0)
VAR b = COALESCE([Budget Gruppe YTD v2], 0)
RETURN r - b
Replace the old measures in the visual.
- If the “6th column” still misbehaves only in Desktop:
- Update Power BI Desktop to latest; test on a different machine.
- Use two table visuals (split columns 1–5 and 6+), or use a field parameter to show one Diff measure multiple times with different display names (avoids multiple distinct measures).
- Ensure no calc groups affect the visual:
- Remove all filters from calc group tables (visual, page, report), and confirm precedence is default.
- If you keep calc groups, avoid dynamic format strings; use static formats.
Environment
- Apply latest SSAS/Power BI engine updates (SSAS 2019 CU / Azure AS equivalent). Known issues with calc groups + dynamic formatting were fixed in later CUs.
- Clear caches: restart SSAS service; in DAX Studio: Clear Cache; in Desktop: File > Options > Data Load > Clear cache.
If DAX Studio outputs correct values while Desktop still shows the 6th column issue, it’s a visual/rendering bug—log it via Help > Feedback and use the split-visual/field-parameter workaround.
Thanks
Haish K
If I resolve your issue. Kindly give kudos to this post and accept it as a solution so other can refer this.
Thank you HarishKM , this was actionable and some good tests. Unfortunatly it was not a solution 😥
I tested in DaxStudio and the error did not appear = This is not a model problem, its a powerbi desktop problem 😃. I can tell my client that this only affects custom measures, not the ones in the model.
I tried clearing the cash as suggested with no luck.
I ran a scrip on the model, and clearned all the formatting from the model > Error persisted
I tried making brand new versions of the measures ([Budget Gruppe YTD],[Realiseret YTD]) and their source measures and made 5diff measures of those. No error, so I was starting to think I had to redo every measure in the model. I made a script that made a copy of each measure, and the old measure got the prefix of "old_", like [old_Realiseret YTD]. (there are 234 measures in this model)
At first glance, there were no errors, and the reports that was build on the model, all still worked as intented. Happy and ready to tell my client, I deletede all the extra 234 measures with the "old_" prefix to clean up
Then the error returned
Updating SSAS2019 is not an option, so I'm stuck at compatibility 1500.
Hi ErikWarming ,
Thank you for detailing your testing process; your insights are very valuable. Based on your results, it seems this issue is specific to Power BI Desktop rather than the data model or DAX logic, as the measures function as expected in DAX Studio.
Duplicating the measures offers only a temporary solution, since the error returns when the original measures are deleted. While newly created measures work properly, the issue recurs after removing the old ones, suggesting a limitation within Power BI Desktop or SSAS 2019 (compatibility level 1500) regarding custom measures.
Given the current compatibility requirements and the inability to upgrade SSAS at this time, this seems to be a Power BI Desktop limitation that may need escalation or further testing in the latest version. For now, the recommended approach is to keep the original measures unused and proceed with the new ones.
Thank you.