Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hi,
I have a measure that counts the total per account and works well when using it in a matrix as it was built for this purpose.
But I do need this same count to be part of a counting category, so I just tried to copy the measure code into a new column on the table but is not working in the same way. Is it related probably to the different context I have in the matrix visual than in the table context?
Thanks,
MR
Solved! Go to Solution.
Hey @mario_ruiz ,
unfortunately it's no just copy and paste to create a calculated column based on the DAX that is used for a measure.
Indeed, this is due to the different context. A calculated column starts without a filter context but with a row context. A measure starts with a filter context. You can transform a row context by using CALCULATE this is called context transition, but you can not transform a filter context into a row context.
This does not mean that there never is a row context when creating a measure.
Nevertheless, you also have to be aware that a calculated column will only be "recalculted" during edit and a data refresh. This means the values will not change when users start interacting with the data.
Hopefully, this helps to tackle your challenge.
Regards,
Tom
Hey @mario_ruiz ,
unfortunately it's no just copy and paste to create a calculated column based on the DAX that is used for a measure.
Indeed, this is due to the different context. A calculated column starts without a filter context but with a row context. A measure starts with a filter context. You can transform a row context by using CALCULATE this is called context transition, but you can not transform a filter context into a row context.
This does not mean that there never is a row context when creating a measure.
Nevertheless, you also have to be aware that a calculated column will only be "recalculted" during edit and a data refresh. This means the values will not change when users start interacting with the data.
Hopefully, this helps to tackle your challenge.
Regards,
Tom
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.
User | Count |
---|---|
85 | |
83 | |
66 | |
61 | |
58 |
User | Count |
---|---|
194 | |
111 | |
105 | |
79 | |
71 |