The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
Hello,
I have a rather conceptual question here:
Given I have several measures which are like
Measure=
Var
Table A=...
Var
Table B=...
return
Calculate ( Sum (sales),
Except )(Table A, Table B))
Now I have a problem with filtercontext so I put these values in a immutable calculated column:
Column = Measures[Measure]
The first one is not problem, but why do I get a circular dependency if I make exactly the same measure, but this time, I
count the orders:
Calculate ( Count (Orders),
Except )(Table A, Table B))
Is there something I can do to modify the Calculate function to make it work?
Best.
Solved! Go to Solution.
The best explanation of what is happening is in:
Avoiding circular dependency errors in DAX - SQLBI
When you use CALCULATE in a calculated column it forces context transition which moves all of the columns included any calculated columns into the filter context. Although your new calculated column doesn't need the first one the presence of CALCULATE makes it depend on it.
The solution is to use ALLEXCEPT or REMOVEFILTER in your CALCULATE statements to prevent them being involved in context transition.
The best explanation of what is happening is in:
Avoiding circular dependency errors in DAX - SQLBI
When you use CALCULATE in a calculated column it forces context transition which moves all of the columns included any calculated columns into the filter context. Although your new calculated column doesn't need the first one the presence of CALCULATE makes it depend on it.
The solution is to use ALLEXCEPT or REMOVEFILTER in your CALCULATE statements to prevent them being involved in context transition.