Forum Discussion
Community ChampionDAX: Puzzling ALL behaviour in context transition
Hi AlB and MattAllington
I did email Jeffrey Wang about this issue recently and he confirmed it is a bug and that it will be fixed in a future release. I don't have a timeframe, unfortunately.
Community ChampionHi v-danhe-msft
There is no error. Both 'Test 1' and 'Test 2' work as you can see in the attached file. I am just trying to understand why the interaction between context transition and ALL() seems to be different in 'Test 1' than in 'Test 2'
Thanks
Microsoft EmployeeHi AlB,
Based on my research, it is due to the simple useage of calculate funtion and the dax engine-The VertiPaq Engine in DAX, when you are using one parameter in calculate function, it takes the existing row contexts (if any) and transforms them into an equivalent filter context.
You could refer to below link:
https://powerpivotpro.com/2014/03/becoming-one-with-calculate/
https://www.microsoftpressstore.com/articles/article.aspx?p=2449192&seqNum=2
And you could refer to the Chapter 5 Understanding CALCULATE and CALCULATETABLE in the book
"The Definitive Guide to DAX: Business intelligence with Microsoft Excel, SQL Server Analysis Services, and Power BI"
Regards,
Daniel He
- MattAllington
My recollection was that Phil_Seamark contacted Jeff Wang about this, and Jeff says it is a bug. Phil, can you confirm?
- AlB
Thanks very much MattAllington
Let's see what @Phil_Seamark says then
- Phil_Seamark
Hi AlB and MattAllington
I did email Jeffrey Wang about this issue recently and he confirmed it is a bug and that it will be fixed in a future release. I don't have a timeframe, unfortunately.
- AlB
Thanks v-danhe-msft
That's however what I explained in my previous post and it does not justify the behaviour
