Deep dive into measure filters in Power BI Desktop
Vložit
- čas přidán 13. 09. 2021
- In this video, we perform a deep analysis of the DAX queries generated by Power BI when you use a measure as a filter in a Power BI visual.
The DAX code generated might show a different behavior whether the measure is part of the values shown in the visual or not.
Article and download: sql.bi/721618?aff=yt
How to learn DAX: www.sqlbi.com/guides/dax/?aff=yt
The definitive guide to DAX: www.sqlbi.com/books/the-defin... - Věda a technologie
Enjoying DAX because of you! Thanks Alberto😀
Thanks Alberto for the detailed explanation!
I enjoyed the thought process and learned A LOT from this valuable video
This is such an excellent explanation!! Thank you
I couldn't find the way, how I thanks to you for your devastating effort to teach. Allah bless you with health, prosperity and knowledge. Ameen. You are
Thank you for democratizing such advanced knowledge. God Bless!
I love this video. Thank you for making it ✅🌹💫
Yes i have seen this very example in a report i built, the difference is now i understand why 😆. Thanks so much.
That's Bananas and interesting to know the behaviour of summarizecolumns() and allselected (). Thank you. 👍
I’ve booked marked this video so I can come back to this again as I didn’t follow the entire concept.
Thank you
instead of modify the base measure [Amt], coudln't you modifiy the [Ranking] measure Inside the RANKX by adding a zero to the CALCULATE ([Amt]...) +0 ?, so the base Measure [Amt] keeps returning blank for future reports?
It looks like a good option. The video is more about how to find the issue and debug it. The solution, then, really depends on the specific requirements. Thanks for bringing this to our attention!
Great 👍
You guys are wearing out my Like button.
TOP PERFORMERS BY YEAR
What will happened if we use Top 2 Descending instead of ranking?
Thanks for this detailed analysis. Worth its time already because of the methodology. However, to be honest, this seems more like a sophisticated illustration of a bug in Power BI. An internal optimization shouldn't justify occasional incorrect results nor cause extra work on behalf of the users. :-(
If powerBi had to calculate every single blank value it'd speed down the engine quite a lot and we'd complaining about how slow PowerBi is.
You are right - PowerBI is full of bugs that are "feature"... on the top of the list there is the so called "Auto Exist"; what is very funny is that MS Excel doesn't have it. It has been introduced in the PowerBI engine. The problem is that Microsoft and their evangelist will never admit them, so they will never be fixed.
Could the alternative solution be to change the ALLSELECTED() function in the Ranking measure 4:37 to ALL()?
Nvm, I don’t think that will work, will still get a blank Amt value
It is a great video! I have a similar issue that uses a measure as a slicer( you use filter, a little different). I am not able to solve the problem. Like your example, if I would like to show all sales that ranked the top 2 for each year, not based on the sum for all years, how can I do it? That is to say, I would like to show values for Apple, Pear, and Banana 100, 200, blank for 2010, blank, 500, 350 for 2011, and 600, 100, blank for 2012. It would be greatly appreciated if you could offer some helps. Thanks
See www.sqlbi.com/articles/filtering-the-top-products-alongside-the-other-products-in-power-bi/
Do you give online courses?
Yes, you can find all our trainings at www.sqlbi.com/training