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!View all the Fabric Data Days sessions on demand. View schedule
Hi everyone!
I'm currently working on an interactive Power BI dashboard and I’ve run into a challenge. I want to include slicers and buttons that allow users to filter by Year, Quarter, and Month.
My goal is to make the experience smooth and conflict-free — for example, avoiding situations where selecting Q1 and August (which belongs to Q3) results in no data.
I’ve tried using bookmarks to toggle between different slicer views, but I’m finding it a bit confusing to manage, especially since there are already quite a few bookmarks involved in the report.
Has anyone implemented something similar? What’s the best way to structure this so users don’t get confused or end up with conflicting filters?
Any tips on DAX logic, slicer design, or UX best practices would be greatly appreciated!
Solved! Go to Solution.
You could just create another conditional formatting measure but this time should be applied to the callout value of the buttons.
Slicer Highlight Color =
IF (
SELECTEDVALUE ( MonthsOnly[Month Short] ) IN VALUES ( Dates[Month Short] ),
"white" --#ffffff for hexadecimal
)
Hi @aziffarhan ,
Thank you for reaching out to the Microsoft fabric community forum.
Thanks for your prompt response
We’d like to confirm whether your issue has been successfully resolved. If you still have any questions or need further assistance, please don’t hesitate to reach out. We’re more than happy to continue supporting you.
Best Regards,
Lakshmi
Hi @aziffarhan ,
We’d like to confirm whether your issue has been successfully resolved. If you still have any questions or need further assistance, please don’t hesitate to reach out. We’re more than happy to continue supporting you.
Best Regards,
Lakshmi
Hi @aziffarhan ,
We’d like to confirm whether your issue has been successfully resolved. If you still have any questions or need further assistance, please don’t hesitate to reach out. We’re more than happy to continue supporting you.
Best Regards,
Lakshmi
Hi @aziffarhan Are the columns coming from the same table? If so, selecting a value in any of the slicers should crossfilter the others unless visual interactions between them have been disabled. If the columns are from different tables, it can cause issues with filtering behavior. As a best practice, use a dedicated date or calendar table that includes all relevant date components (such as date, year, month, quarter, day, week number, etc.).
Hi @danextian, thank you so much for your help! I really appreciate it.
There are a few things I still need help with.
Firstly, all the columns I’m using are from the same table. I’ve already created a Date Hierarchy consisting of Year, Quarter, Month, and Day.
What I’d like to achieve is the following behavior:
Is there a way to implement this kind of synchronized selection behavior in Power BI? I’d really appreciate any guidance or suggestions you can offer.
Thanks again!
Have you checked if visual interactions are enabled for those slicers? With or without hierarchy, as long as the interaction is enabled, you will get the same behaviour as in the image in my initital response. Also, please check if indeed the columns are from the same table - it could be a column with the same name but from another table.
Hi @danextian, thanks again for your help!
The interactions are currently disabled, and there are a few reasons why I chose to do that.
I want the Month slicers to be selectable, not just displayed after clicking on a Quarter. At the same time, I need all buttons/slicers to be visible at all times. For example, when I select Q1, I want Jan, Feb, and Mar to be highlighted or selected, but I don’t want the other months to be hidden. I want all months to remain visible, regardless of the selection.
I’d really appreciate your help in figuring out how to achieve this behavior. Also just to add, a feature where I can select any months that I want without having to select a quarter is also needed. Whenever the user select a month, the respective quarter will also be selected, while the other quarter will be shown but not selected.
Feel free to let me know if more context is needed for your understanding.
Thank you!
If you disable the interaction then you can't really expect them to sync. There is currently no option to cross-highlight instead of cross-filtering the interaction between slicers. The default behaviour of a slicer to is to cross-filter even non-slicer visuals. That said, your workaround is to use dimensions that are not directly related to each other - quarter coming from the regular table and months from a months only table but still related to fact. Your diagram would look like below.
Cross-highligting will be done via conditional formatting. Create a measure that will check whether the months in MonthsOnly are currently visible in Dates table
Slicer Highlight Color =
IF (
SELECTEDVALUE ( MonthsOnly[Month Short] ) IN VALUES ( Dates[Month Short] ),
"#ADD8E6"
)
Crossfiltering/highlighting from months to quarter also uses a measure in a visual filter or conditional formatting.
Please see the attached sample pbix.
Hi @danextian, thanks for your help, again.
Is there any way that I could make the font color in the button slicer becomes white after it has been highlighted. For example, when Q1 is selected, Jan, Feb and March will be highlighted and the font will be white (#FFFFFF).
I would appreciate it if you could help me with these inquiries.
Thank you.
You could just create another conditional formatting measure but this time should be applied to the callout value of the buttons.
Slicer Highlight Color =
IF (
SELECTEDVALUE ( MonthsOnly[Month Short] ) IN VALUES ( Dates[Month Short] ),
"white" --#ffffff for hexadecimal
)
It still doesn't seem to work. Whenever I tried to select 2 quarters at the same time, the font becomes black again (in month). Really appreciate it if you could help me with these.
This approach is simple to set up, requires no complex DAX, and is very intuitive for the end-user.
1. Build a Proper Calendar Table
The foundation of any good report is a solid calendar table. Make sure you have a table in your model with at least the following columns. This table should be marked as a date table and have a relationship to your data.
2. Create a Hierarchy
A formal hierarchy will make the slicer "aware" of the relationship between the fields.
3. Configure the Slicer Visual
This single slicer will now provide a guided, drill-down experience:
Users can navigate back up the hierarchy using the "Drill up" arrow in the slicer's header. This design makes it impossible to create a conflicting selection and eliminates the need for any complex bookmarks or DAX.
If this explanation and solution resolve your issue, please like and accept the solution.
Hi @Sandip_Palit, thank you for your help!
Unfortunately, I don’t think a drill-down slicer is what I’m looking for at the moment. I’d like the slicer to display all Years, Quarters, and Months directly, so users can click on any of them without needing to drill down step by step.
I’d really appreciate your help with this setup.
Thank you!
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!