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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
When two measures that have a very similar looking but different calculation both use TREATAS with a variable as the first TREATAS parameter and are used in the same visual the output of one of the measures will incorrectly be a duplicate of the output of the other measure. This looks like an incorrectly applied DAX fusion optimization, which measure output gets duplicated seem to depend on which measure you add to the visual first.
This is what the output should look like:
Here is the incorrect output:
Here is the DAX code of the two measures:
Here is the data from the simple 2 table data model used to demonstrate the problem.
I can provide a PBIX file that demonstrates the problem if needed.
It is disappointing that this got moved into the DAX Help section when I created it as in Issue and I am trying to report a DAX engine optimization bug.
Hi @MichaelOgaz
The Date column in the table visual is coming from which table?
Hi,
Is there a specific reason you want to use TREATAS here?
If you want to display running total and day values there are simpler methods. e.g. with the new visual calculations:
Data:
Measure 27 is just SUM
Proud to be a Super User!
Hi @ValtteriN
The example data and measures I posted in this Issue are not the real world situation where I have encountered this bug. This is a set of data and measures just used to demonstrate the problem in a simple and direct way.
Join the Fabric FabCon Global Hackathonโrunning virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.
User | Count |
---|---|
10 | |
7 | |
5 | |
4 | |
3 |
User | Count |
---|---|
12 | |
12 | |
10 | |
9 | |
9 |