Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Hi Everyone,
I wrote a DAX Measure:
Solved! Go to Solution.
In your DAX measure, the FILTER function is able to read [Total Compliance Rate] because it is referring to the measure [Total Compliance Rate] that exists in your data model, not the column you created in the SUMMARIZE function.
When you use SUMMARIZE, you are creating a new table with a summarized view of your data, and you can add calculated columns to this table. However, these calculated columns are not directly accessible outside the context of the SUMMARIZE function. Instead, DAX continues to use the measures and columns defined in your data model.
Proud to be a Super User! |
|
In your DAX measure, the FILTER function is able to read [Total Compliance Rate] because it is referring to the measure [Total Compliance Rate] that exists in your data model, not the column you created in the SUMMARIZE function.
When you use SUMMARIZE, you are creating a new table with a summarized view of your data, and you can add calculated columns to this table. However, these calculated columns are not directly accessible outside the context of the SUMMARIZE function. Instead, DAX continues to use the measures and columns defined in your data model.
Proud to be a Super User! |
|
Thank you for your response.
May I ask what you mean by data model?
It means rest columns, measure and calculated columns in your report
In your DAX measure, [Total Compliance Rate] is a measure that exists in your data model. When you reference [Total Compliance Rate] in your FILTER function, DAX understands it as the measure defined in your data model, not the column you created in the SUMMARIZE function. This is why the filter works correctly.
Proud to be a Super User! |
|
Thank you!