I learned from your training that the Calculate() function always uses a table for filtering. This made understanding how the feature works much easier. And here, too, a very good understanding arises precisely because you convert the condition into a table. Thanks Marco.
Dude, this was a great video. although a lot of us might have came up with the same solutions by trial and error but I bet many of us, including myself, didn't know what the hell is happening underneath. Cheers!
Hi, thanks for sharing this amazing content with us. May I ask something? I am not sure if I understand the mechanism that generates this result. I am trying to understand the mechanism of this operation in terms of expanded tables. Well, if my concepts are correct: 1. Cross-join will maintain the data lineage between the tables. 2. Beside the result of the cross-join is a table with two columns; in more internal aspects, the cross-join generates/activates an expanded table with the fact in the middle and the dimensions in the boards. 3. This expanded table can now be filtered considering the two columns in the dimensions tables. Have a great weekend! :-)
This will be a + 50k video in no time ! 2 questions though 1) any plans Microsoft is going to use yours and other MVPs knowledge to make these error message clearer highlighting potential solutions? 2) is it safe to say when using variables you mitigate risk of running into errors. are there any scenario's why you should not use variables?
An excellent Video. Thank you!!!Can you help me please to resolve a problem I'm having with filters? I tried to post my problem on forums but no one answers me and I'm really stuck. thanks in advance
What is the Total row in the last two examples (profitable Customers and Profitable Stores) telling us? it is not a sum of the numbers above, nor is it an average.
A predicate is a logical condition, which can be translated into a table automatically when it is used in a filter argument of CALCULATE. A filter is always a table. The predicate converts into a table only in that specific condition (filter argument of CALCULATE or CALCULATETABLE).
I learned from your training that the Calculate() function always uses a table for filtering. This made understanding how the feature works much easier. And here, too, a very good understanding arises precisely because you convert the condition into a table. Thanks Marco.
Hello, which Training you have taken?
Thanks for shedding light on these common calculate errors!
Thoroughly enjoyed, Awesome explanation . Thanks Marco
An excellent Video. Thank you!!! Please continue to make videos with this approach.
This was so helpful. I'm certain I've seen every one of these errors over the years. Sending to my coworkers to make their life easier.
you and Alberto are the best. still keep learning from your training and following your video on youtube that much help to understand DAX. thanks!
well, now we can enjoy DAX! thank you marco!
What a treasure- video ! Thanks for opening our eyes
Always wondered what that PLACEHOLDER error meant. Great video covering useful techniques and concepts from the most powerful function in DAX! :)
Brilliantly explained! Please make more videos of such nature-- thanks!
Dude, this was a great video. although a lot of us might have came up with the same solutions by trial and error but I bet many of us, including myself, didn't know what the hell is happening underneath. Cheers!
Precisely my thought
Thanks Marco, please keep up the great work. This channel is so useful to whoever wants to learn DAX!!!!
Very informative. As always. Thank you very much.
Thanks! That fixed my issue with the placeholder error.
Thank you so much Marco. Very insightful!
As always great stuff from SQLBI, many thanks.
Love the way you explain things. :)
Hi, thanks for sharing this amazing content with us. May I ask something? I am not sure if I understand the mechanism that generates this result.
I am trying to understand the mechanism of this operation in terms of expanded tables. Well, if my concepts are correct:
1. Cross-join will maintain the data lineage between the tables.
2. Beside the result of the cross-join is a table with two columns; in more internal aspects, the cross-join generates/activates an expanded table with the fact in the middle and the dimensions in the boards.
3. This expanded table can now be filtered considering the two columns in the dimensions tables.
Have a great weekend! :-)
Very useful video,thx
This will be a + 50k video in no time ! 2 questions though
1) any plans Microsoft is going to use yours and other MVPs knowledge to make these error message clearer highlighting potential solutions?
2) is it safe to say when using variables you mitigate risk of running into errors. are there any scenario's why you should not use variables?
1) who knows
2) variable does not save you from errors, but they make the code easier to read and to debug!
Thank you very much!
An excellent Video. Thank you!!!Can you help me please to resolve a problem I'm having with filters? I tried to post my problem on forums but no one answers me and I'm really stuck. thanks in advance
master class
What is the Total row in the last two examples (profitable Customers and Profitable Stores) telling us? it is not a sum of the numbers above, nor is it an average.
Hi Sir,
Is there any replacement for allselected function since it is not working in custom tooltip?
Thanks &Regards
Nikhil
Brilliant!
Ciao, didn't know that I am your friend. BANANAS!
Great video. Filter argument of CALCULATE or predicate is the same terminology?
A predicate is a logical condition, which can be translated into a table automatically when it is used in a filter argument of CALCULATE. A filter is always a table. The predicate converts into a table only in that specific condition (filter argument of CALCULATE or CALCULATETABLE).
@@SQLBI thank you! Now I understand more, why context transition is hard to master.
i didn't understand the removefilters logic can someone explain ???
I suggest that you review how the filter context works - look at the videos on this series: www.sqlbi.com/series/the-whiteboard/