Matt Allington's Blog 🌐 - exceleratorbi.com.au/slicer-values-dont-clear-after-changing-a-second-slicer/ Download the Power BI file ⬇ - goodly.co.in/non-sticky-slicer-trick-power-bi Let me teach you DAX & Data Modeling in Power BI in the most simple and effective way. 📊 - goodly.co.in/learn-dax-powerbi/
🤯 DAAAAMMMNNNN!!! Well done, Chandeep! 👍 Thank you for the EPIC solution for this annoying quirk! 😊 Gotta update all of my reports with paired slicers now...
Thank you very much! especially field parameters: show values. hot tip! But... since I am not that good at writing M, I tried to make this helper table with the GUI. It did work but it was sometimes hard coded. Tihs is how I did this: I made two queries: one unique products, one unique brands. Then I merged them (cross join). Then I added an index column and a MOD collumn to get numbers from 0 to 11. Then pivot and don't aggegate. This is easier but your solution is dynamic, as it should be..😉
Nice again, but table Bands is created from parameter, what if we get more rows in table helper, then should manually add in table bands, or is it possible get dynamically
It helped to resolve one of my Issues, Thanks for that. I have one query, lets say I have Same Products in the different bands then one 2 one Relationship will not work. I know according to your example it's a stupid question 😂.
Chandeep, thanks for the useful information you provide on your channel. I have learnt a lot from you. If I should create the table for the Field Parameter slicer in Excel, for instance, and create the relationships between the tables as you did after creating the slicers, will it work the same way?
Hello. I have a problem here. Although it looks like you have a table and using power query to solve a sticky slicer issue, I am connected to a live semantic model and still facing the sticky slicer problem. Is there any way of working out through the sticky slicer when connected to a semantic model? You wont be having those tables and power queries in a semantic model.
Using cascading filters would be easier. INT (NOT ISEMPTY(INSERT FACT_Table_Here)). Add this onto all slicers and then filter on right hand Navigation Page = 1.
do you have any other trick to do this actually my main slicer is created with a field parameter only and for the sub-slicer I cant reuse the field parameter method....
great solution for this case. however i think it will not work efficiently (if at all), if you have a lot of data. like thousands of projects in slicer A and in slicer B all of the tasks of these projects. Maybe I'll give it a try though
![[FULL EP.16] เซียนพาลุย "เผือก-ฟรอยด์" กรี๊ดลั่น จนปูหนี | เฮ็ดอย่างเซียนหรั่ง | One Playground](http://i.ytimg.com/vi/FsqUvwS3b-Y/mqdefault.jpg)
Wow!! Never knew that field parameters can show the field values also. With this you have solved my problem. Thank you, Chandeep.
Matt Allington's Blog 🌐 - exceleratorbi.com.au/slicer-values-dont-clear-after-changing-a-second-slicer/
Download the Power BI file ⬇ - goodly.co.in/non-sticky-slicer-trick-power-bi
Let me teach you DAX & Data Modeling in Power BI in the most simple and effective way. 📊 - goodly.co.in/learn-dax-powerbi/
This is a great video workflow, especially the problem section at the start
I was looking for this solution last week... With this trick you have solved my problem
🤯 DAAAAMMMNNNN!!! Well done, Chandeep! 👍 Thank you for the EPIC solution for this annoying quirk! 😊 Gotta update all of my reports with paired slicers now...
This is out of this world! Will give it a shot
Beautiful work once again Chandeep! Thank you :)
You are a PQ ninja!
Thank you very much! especially field parameters: show values. hot tip! But... since I am not that good at writing M, I tried to make this helper table with the GUI. It did work but it was sometimes hard coded. Tihs is how I did this: I made two queries: one unique products, one unique brands. Then I merged them (cross join). Then I added an index column and a MOD collumn to get numbers from 0 to 11. Then pivot and don't aggegate. This is easier but your solution is dynamic, as it should be..😉
Helper query ❤ love this terminology I’ve been using it for awhile but was not sure how to call this lol anyhow brilliant that you my friend
😁
Interesting.
Haven’t looked into this in depth.
Would the pivot or unpivot of the dimension table be a quicker option ?
Nice again, but table Bands is created from parameter, what if we get more rows in table helper, then should manually add in table bands, or is it possible get dynamically
It helped to resolve one of my Issues, Thanks for that. I have one query, lets say I have Same Products in the different bands then one 2 one Relationship will not work.
I know according to your example it's a stupid question 😂.
Another interesting one as always,Not to miss the time 6 PM IST.😀
😉
That is amazing tricks. When you created helper table, can't we do unpivoting directly or that will not work?
Chandeep, thanks for the useful information you provide on your channel. I have learnt a lot from you. If I should create the table for the Field Parameter slicer in Excel, for instance, and create the relationships between the tables as you did after creating the slicers, will it work the same way?
I have an error in Band measure : The expression refers to multiple columns. Multiple columns cannot be converted to a scalar value.
Brilliant !! Thanks much.
Great video again, thank you Chandu
Amazing solution
Another great one Chandeep!
Thanks Chris 😄
Awesome 💯 i want to lean it... In cases you provide online training 😮😊
Superb solution ❤
Hello. I have a problem here. Although it looks like you have a table and using power query to solve a sticky slicer issue, I am connected to a live semantic model and still facing the sticky slicer problem. Is there any way of working out through the sticky slicer when connected to a semantic model? You wont be having those tables and power queries in a semantic model.
Using cascading filters would be easier. INT (NOT ISEMPTY(INSERT FACT_Table_Here)). Add this onto all slicers and then filter on right hand Navigation Page = 1.
Really dammed awesome! I can't say it different.
do you have any other trick to do this actually my main slicer is created with a field parameter only and for the sub-slicer I cant reuse the field parameter method....
This is really awesome ❤
More like pretty dam Brilliant.
Awesome !!!! Thankyou🙏
Seems any question in PBI had the same answer, fields parameters
Please create video for power query most asked interview questions
great one sir, keep it up
Very interesting one.. 👍
Yes, it is pretty damn awesome
Great again
Genius ❤
Awesome 😍
👍👍👍
great solution for this case.
however i think it will not work efficiently (if at all), if you have a lot of data. like thousands of projects in slicer A and in slicer B all of the tasks of these projects.
Maybe I'll give it a try though
Outstanding. Thx