Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hello everyone,
I try to have synchronized date slicers but i couldn't make it happen ,
Here's some problems :
Case 1 : i clicked on janvuary 2024 but in the between slicer it keep showing 7 july as max date
Case 2 : i clicked on 2023 but it still shows 2024 in between slicer
any suggestions??
Thank you
Solved! Go to Solution.
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.
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.
You need to turn on Edit Interaction between the slicers from the format Tab. Once it is set to filter the required slicer, you will see the date slicer will filter based on the selected month
Hello, you need to enable sync slicers feature, which should be done and then in the Power BI view tab, go to sync slicers:
https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-slicers?tabs=powerbi-deskt...
https://learn.microsoft.com/en-us/power-bi/developer/visuals/enable-sync-slicers
Hello @lszymk97 thanks for the reply
it's already done + i'm working on a single page and the filters are already synchronized
the only problem is that the "between" slicer is not showing the same values as the other slicers
like this exemple :
Did you ensure that all your date columns across different tables are properly connected ? Misaligned relationships can cause inconsistencies and also please check whether date formats are the same. Alternatively you can try to use DAX measure for date logic Instead of relying on raw date columns
Actually the 3 slicers are from the same table "date"
i've managed to make it appear correctly for the year slicer, when i select another year it change automatically but when changethe max date slicerand i select a month like this exemple it must shows 31/01 but it shows 14/02
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
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.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 53 | |
| 51 | |
| 36 | |
| 15 | |
| 14 |
| User | Count |
|---|---|
| 92 | |
| 75 | |
| 41 | |
| 26 | |
| 25 |