Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hello Power BI Community!
I'm working on an NPS Admin Overview dashboard and would love your creative input on a design challenge I'm facing.
Current Situation: I have a comprehensive dashboard that displays survey data, NPS trends, and detailed breakdowns. I need to add two toggle buttons (Provider View and Location View) that will control what data is displayed in the main content area.
The Challenge: I'm struggling with where and how to optimally place these view control buttons. The dashboard is already fairly dense with:
I've mocked up the buttons at the bottom of the main panel (see screenshot), but I'm not entirely satisfied with this placement.
What I'm Looking For:
I'm completely open to redesigning sections of the dashboard if it results in a better overall experience!
Thanks in advance for any insights you can share! 🙂
Solved! Go to Solution.
First let me say Thank You to everyone that replied, means the world to me.
After review of what everyone said, I took a little from everyone and was able to build bookmark buttons that the Leadership loved.
So thank you greatly, and i will be using some of your ideas on new dashboard (reports)
First let me say Thank You to everyone that replied, means the world to me.
After review of what everyone said, I took a little from everyone and was able to build bookmark buttons that the Leadership loved.
So thank you greatly, and i will be using some of your ideas on new dashboard (reports)
Hi @MSchlaudraff,
Thank you @GeraldGEmerick, @SavioFerraz, @Nabha-Ahmed and @wardy912 for your prompt responses.
we haven't heard back from you regarding our last response and wanted to check if your issue has been resolved.
Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum!
Hi @SavioFerraz
⭐ 1. Place the Toggle in the Header (Best Practice)
The header area is the ideal location for global view-mode controls.
Why this is best:
Users expect “global dashboard settings” at the top
It’s visible immediately
Works well even when scrolling
Matches UI standards from Microsoft, Salesforce, Tableau, etc.
How to implement:
Add a 2-button toggle (Provider | Location) to the top-right, beside your date slicers
Style it as a segmented control / pill toggle
Reduce slicer width to make space (or collapse slicers into a panel)
This is the #1 industry-standard placement.
---
⭐ 2. Convert the toggle into a Ribbon Section (Secondary Header)
If your top header is already full, create a thin sub-header just below the slicers.
---------------------------------------------------
[ Date Slicers ] [ Filters ]
---------------------------------------------------
Provider | Location ← toggle here
---------------------------------------------------
NPS Trend Chart
Pros:
Dedicated space
Very clean visual separation
Still “global” in meaning
---
⭐ 3. Convert Slicers into a Collapsible Filter Panel
If space is the problem, free up the header:
Steps:
Move all filters into a left or right filter panel (collapse/expand using a button)
Place your 2-option toggle in the space you just freed up
Pros:
Dashboard becomes cleaner
More room for buttons
Matches modern BI design patterns (Looker, Fabric, Snowflake dashboards)
---
⭐ 4. Use a Floating Overlay Toggle (Advanced UI pattern)
Place the toggle as a floating pill on the top-right corner of the main visual area.
Pros:
Always visible
Saves full-page layout space
Modern “app-style” feel
Doesn’t interfere with other visuals
Tips:
Use semi-transparent background
Keep it small and minimal
---
⭐ 5. Combine Provider/Location into a Single Dropdown Slicer Instead of Two Buttons
Sometimes UX gets simpler if you reduce the visual component count.
Example:
Replace buttons with a small “View Mode” slicer
Use a custom visual (Segmented Slicer or Chiclet Slicer)
Pros:
Cleaner than buttons
Consistent with other filters
Easily fits in the header
---
⭐ 6. Restructure the page: Make Provider | Location a Page-Level Mode
This works when the dashboard has two fundamentally different contexts.
Pattern:
Keep the toggle in the header
Use bookmarks or field parameters to fully swap the content
The entire page layout adapts to the selected view
Pros:
Makes the dashboard feel like a 2-in-1 app
Highly intuitive for admin users
Great when content differs significantly
@MSchlaudraff A design that I have seen used successfully is to make the buttons appear to be tabs in the header area. So for you that would be in the blue area. I would probably move the gray box in that area over to the left and then do some formatting of the buttons that make them appear to be tabs on the far right side of the header area. You would actually have 4 buttons, each button would actually have 2 overlapping/stacked buttons that you would control via bookmarks so that you have a different color depending on whether the tab is active or not. In an active state, the background color would be white to make it merge with the main content area, thus looking like an actual tab. You can adjust the state for hovering over the "tabs" as well.
I tend to use a slicer panel with the button slicer being used for the majority of my 'either/or' choices.
It doesn't interfere with the overall visuals, and if you want it be completely removed until required, you can always set up a bookmark that the user can select to view options. Here's the bottom of my slicer panel.
I place all slicers on a shape to the right or left of the page that is a different colour to the page background, but still fits the theme.
--------------------------------
I hope this helps, please give kudos and mark as solved if it does!
Connect with me on LinkedIn.
Subscribe to my YouTube channel for Fabric/Power Platform related content!
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 |
|---|---|
| 55 | |
| 45 | |
| 38 | |
| 16 | |
| 14 |
| User | Count |
|---|---|
| 87 | |
| 69 | |
| 38 | |
| 29 | |
| 26 |