I love the way you explain things, always very clear and with dedication. Keep posting these very informative videos, whenever I have a problem I always search for Nestor, and “boom” I always get a solution. Regards John Copperstone, Malta
Thank you so much! I had a remark about case 4.1 . What if I used the Query Editor, duplicated the claims table and filtered the Category and Products Claimed table to just the 3 categories and 5 products claimed and saved it as a new table, wouldn't it perform the same function as ALL?
Shruti, Thanks for your question. Yes, we can also use your approach. For this particular case, I am using FILTER to show that it is a table function. If we have to pick one method or another, we might want to check the performance by using DAX Studio. Great approach as well!
Have a qq: what was the reason using All in last example ? As far as I noticed we do not have any filter context in the visual to be overwritten by ALL. Can't we just go with coffee makers without using all there?
Hey Michal, Thanks for stopping by. Yeah, if we don't have any filter affecting a column or table, the result would be the same. However, I'd encourage everyone to use the ALL function for more complex calculations.
so you used the formula Total Premium= sumx(All(claims),claims[collected premium])..here i have two questions..what happens if we dont use All in the above formula..secondly, what happens is i use sum in place of sumx..
Prasad Nori, Thanks for stopping by. Good questions. 1. The purpose of using ALL was to remove any filter in the claims table. If we don't use it and there are filters applied to that table, we might expect different results. 2. The SUMX function gives us more flexibility to apply additional calculations. For example, I could have done: Premium = SUMX (All (claims,), claims[collected premium * 2] In this tutorial, since we are only aggregating values from the Collected Premium column, we could have used SUM as well.
@@NestorAdrianzen at 10.25 when you use SUMX( table, expression) you choose " collected premium" in expression part of SUMX. could you please advise if you created "collected premium" measure in advance?
Hi experts , I just publish a report for 10 users and except 1 all are able to view. There is no role change or permission changes . How can i trouble shoot it . Can anyone please help me with it. Can you suggest the basic issues we face in work
RAGHU NADH AMARA. Thanks for your question. Do you know if a dynamic Row-Level Security has been implemented? Have you shared your report with all of them? if so, perhaps, you will need to provide them access to the Workspace [where the report is published ] as well. I hope it helps!
Prabhat, You are correct! We could have written the last measure as follow as well: Claim Cost Coffee Maker: CALCULATE ( SUM(Claims[Claim Cost]), Claims[Product claimed = "Coffee Maker" ) I wanted to include ALL in this measure just to give everyone awareness about the use of ALL as part of the CALCULATE function.
