The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi, my name is Marta and I have a problem with the "between" slicer. I will put an example.
I have flanged joints of different sizes that work under different temperatures. When there are no filters, the ranges of temperature go from 0ºC to 400ºC, which is the lowest and highest value of my data. If I set a filter to just analyze flanges among 10" to 20" we will se that my database temperatures go from 0ºC to 200ºC. When I use a “drop-down” or ”vertical list” filter to select the temperature there is no problem, the problem comes when I change the filter appearence to "between", when the previous size filter stops working on the temperature one and the range is 0ºC to 400ºC again.
I have already reached Microsoft Support and the told me that it was a development issue, so I was hoping I could contact a developer, since I'm sure that I am not the only one who encountered this problem.
As you can see in the first picture, with thw "between" slicer, the range is the lowest and highest value of my data (which is not correct because I'm filtering other stuff), but if I change back to the “drop-down” or ”vertical list” filter, ir works correctly and the other filters DO affect this one.
Thanks in advance for your help and I look forward to hearing from you.
Solved! Go to Solution.
Thanks for the reply from saud968 , please allow me to provide another insight:
Hi, @martaparapar
Thanks for reaching out to the Microsoft fabric community forum.
1.Firstly, you are correct. In Power BI, the interaction design of the "between" type date slicer is indeed different from other types of slicers (such as tile slicers). According to Power BI's design documentation, the "between" type slicer is used to select a date range and does not automatically respond to the filtering conditions of other slicers. This is because the "between" type slicer is primarily intended to provide a fixed date range selection rather than dynamically responding to changes from other slicers.
Below are the screenshots of the relevant documentation:
For more details, please refer to:
Create a numeric or date range slicer in Power BI - Power BI | Microsoft Learn
2.Secondly, I suggest using page-level filters as an alternative:
The only downside is that you cannot display it as a visual object like a slicer, but filters are supported in the service.
For more details, please refer to:
Add a filter to a report in Power BI - Power BI | Microsoft Learn
3.Finally, if you feel that performance needs improvement, you can submit an idea and wait for users with similar needs to vote for it, helping you achieve this idea more quickly. Many features of our existing products are designed and upgraded based on customer feedback. As demand increases, this issue may be addressed in the future.
Here is the link to submit your idea:
Best Regards,
Leroy Lu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for the reply from saud968 , please allow me to provide another insight:
Hi, @martaparapar
Thanks for reaching out to the Microsoft fabric community forum.
1.Firstly, you are correct. In Power BI, the interaction design of the "between" type date slicer is indeed different from other types of slicers (such as tile slicers). According to Power BI's design documentation, the "between" type slicer is used to select a date range and does not automatically respond to the filtering conditions of other slicers. This is because the "between" type slicer is primarily intended to provide a fixed date range selection rather than dynamically responding to changes from other slicers.
Below are the screenshots of the relevant documentation:
For more details, please refer to:
Create a numeric or date range slicer in Power BI - Power BI | Microsoft Learn
2.Secondly, I suggest using page-level filters as an alternative:
The only downside is that you cannot display it as a visual object like a slicer, but filters are supported in the service.
For more details, please refer to:
Add a filter to a report in Power BI - Power BI | Microsoft Learn
3.Finally, if you feel that performance needs improvement, you can submit an idea and wait for users with similar needs to vote for it, helping you achieve this idea more quickly. Many features of our existing products are designed and upgraded based on customer feedback. As demand increases, this issue may be addressed in the future.
Here is the link to submit your idea:
Best Regards,
Leroy Lu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Try to Use a Custom Measure: Create a measure that dynamically calculates the minimum and maximum values based on the selected filters. Then, use that measure in your slicer.
Best Regards
Saud Ansari
If this post helps, please Accept it as a Solution to help other members find it. I appreciate your Kudos!