Forum Discussion
Synchronized slicers
- Anonymous2 years ago
Thanks for the reply from Prince_Rajkumar and lszymk97 please allow me to provide another insight:
Hi, mmannai
Can you tell me if your problem is solved? If yes, please accept Prince_Rajkumar's reply as solution.
First of all, I think Prince_Rajkumar answer is correct. Because I also encountered a similar problem in my actual measurements.
But when I checked if the interaction between the visualizers was turned off, I found that the interaction between slicers created by automatic time and slicers created at normal time was turned off by default. On the contrary, the interaction between slicers created at normal time and slicers created at automatic time is turned on normally.
Here are my actual results:
So you can click on the slicer visualization and click on the following image to enter the visual's interaction page, and then modify it:The following documents are what we hope will help you:
Change how visuals interact in a report - Power BI | Microsoft LearnAuto date/time in Power BI Desktop - Power BI | Microsoft Learn
Please find the attached pbix relevant to the case.
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.
- Anonymous2 years ago
Hi, mmannai
Thanks for letting us know your user experience. According to your case description, I do understand how frustrated you are now.Nevertheless, according to our measured results, I feel regretful to inform you that it turns out to be a by-design one.
When you select a slicer, then select another slicer, filter to a non-existent value, and then change the value of the slicer, it will be saved normally, but the slicer result is based on the latest filter range.
Here are links to similar issues:
filter showing default value which is not there if... - Microsoft Fabric Community
If you feel that performance needs to be improved, you can also submit an idea on
https://ideas.fabric.microsoft.com/ and wait for users with the same needs as you to vote for you and help you realize the idea as soon as possible. Many features of our current products are designed and upgraded bed on customers’ feedback. With requirements like this increase, the problem may well be released in the future.
Thanks for your understanding.
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 Prince_Rajkumar and lszymk97 please allow me to provide another insight:
Hi, mmannai
Can you tell me if your problem is solved? If yes, please accept Prince_Rajkumar's reply as solution.
First of all, I think Prince_Rajkumar answer is correct. Because I also encountered a similar problem in my actual measurements.
But when I checked if the interaction between the visualizers was turned off, I found that the interaction between slicers created by automatic time and slicers created at normal time was turned off by default. On the contrary, the interaction between slicers created at normal time and slicers created at automatic time is turned on normally.
Here are my actual results:
So you can click on the slicer visualization and click on the following image to enter the visual's interaction page, and then modify it:
The following documents are what we hope will help you:
Change how visuals interact in a report - Power BI | Microsoft Learn
Auto date/time in Power BI Desktop - Power BI | Microsoft Learn
Please find the attached pbix relevant to the case.
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.
Thank you Anonymous for your detailed response.
I tried working with the example you sent, "time.pbix." It worked perfectly until I changed the max date in the between slicer. After that, the other slicer doesn't work correctly, as shown here:
As you can see the max value is not showing correctly if changed manually , you need to reset it after you change it
- Anonymous2 years agoNot applicable
Hi, mmannai
Thanks for letting us know your user experience. According to your case description, I do understand how frustrated you are now.Nevertheless, according to our measured results, I feel regretful to inform you that it turns out to be a by-design one.
When you select a slicer, then select another slicer, filter to a non-existent value, and then change the value of the slicer, it will be saved normally, but the slicer result is based on the latest filter range.
Here are links to similar issues:
filter showing default value which is not there if... - Microsoft Fabric Community
If you feel that performance needs to be improved, you can also submit an idea on
https://ideas.fabric.microsoft.com/ and wait for users with the same needs as you to vote for you and help you realize the idea as soon as possible. Many features of our current products are designed and upgraded bed on customers’ feedback. With requirements like this increase, the problem may well be released in the future.
Thanks for your understanding.
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.