Forum Discussion
Powerbi Default view
I have a report with a single-select slicer that lets users choose between two views: Historical or Predicted.
The report has 5 pages, each representing a different time granularity:
Hourly & Daily Pages: Use "Between" date slicers.
Weekly Page: Uses a slicer showing week ranges (e.g., "20-26 Jul 2026"), Month, and Year. (multi-select slicer)
Monthly Page: Uses a dropdown slicer with Month-Year values (e.g., "Jun 2026"). (multi-select slicer)
Yearly Page: Uses a Year slicer. (multi-select slicer)
The Goal:
I need the dashboard to load a specific "default view" based on the user's selection in the Historical/Predicted slicer:
If Historical is selected: The date filters across all pages should default to the maximum available date in the historical dataset.
If Predicted is selected: The date filters should default to the current date (TODAY()).
This logic should scale to the respective granularity of each page (Weekly, Monthly, Yearly).
My Tableau Approach vs. Power BI:
In Tableau, I would typically handle this by creating Start and End Date parameters driven by Min/Max calculated fields, and then applying a boolean filter to the sheet (Date >= Start Date AND Date <= End Date).
How can I achieve this dynamic default behavior in Power BI? Is there a standard workaround or DAX pattern to handle default date states when a page loads, without losing the ability for the user to manually override the slicer?
Any advice or recommended patterns would be greatly appreciated. Thank you!
Hello g-zakkour,
Thanks for the follow-up.
If your goal is for the date slicer itself to automatically change its selected value based on the Historical/Predicted slicer, then unfortunately this isn't supported in Power BI. DAX measures cannot programmatically set or update a slicer's selected value.
The approach I suggested is intended to provide the same report behavior rather than changing the slicer itself:
- Keep the date slicer available so users can manually override the date.
- Use an IsDefaultPeriod measure (or incorporate the logic into your measures) to display the latest historical date or TODAY() by default in the visuals.
- Once the user selects a different date, that selection naturally takes precedence.
If having the slicer automatically change is a hard requirement, the closest alternatives are:
- Separate Historical and Predicted report pages.
- Bookmarks with predefined slicer states.
- A custom navigation experience.
Could you clarify whether your requirement is:
- The visuals should show the correct default period, or
- The date slicer itself must automatically change its selected value?
That will help determine the best approach.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.
5 Replies
Hello g-zakkour,
Unlike Tableau parameters, Power BI slicers don't support dynamically changing their default selected value based on another slicer (such as Historical vs. Predicted).
A common approach is:
Create a disconnected table for the Historical / Predicted selection.
Create DAX measures that determine the "effective" default date based on the selected mode:
Historical → Maximum available historical date.
Predicted → TODAY()
Use these measures to create a flag measure (for example, IsDefaultPeriod) that returns 1 for the desired date/week/month/year.
Apply this measure as a visual-level filter (or incorporate it into your calculations), while still allowing users to manually override the slicers.
This pattern preserves the initial default behavior while keeping the report interactive. It also scales well across daily, weekly, monthly, and yearly pages by adjusting the DAX logic for each level of granularity.
If you need the slicer selection itself to change automatically, that isn't currently supported in Power BI. In that case, you'd typically use bookmarks, separate report pages, or navigation buttons to provide different default entry points.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.hello Omkar_1712
so after doing the calculations i apply it to all the visuals including the date picker? or without the date picker?Hello g-zakkour,
Thanks for the follow-up.
If your goal is for the date slicer itself to automatically change its selected value based on the Historical/Predicted slicer, then unfortunately this isn't supported in Power BI. DAX measures cannot programmatically set or update a slicer's selected value.
The approach I suggested is intended to provide the same report behavior rather than changing the slicer itself:
- Keep the date slicer available so users can manually override the date.
- Use an IsDefaultPeriod measure (or incorporate the logic into your measures) to display the latest historical date or TODAY() by default in the visuals.
- Once the user selects a different date, that selection naturally takes precedence.
If having the slicer automatically change is a hard requirement, the closest alternatives are:
- Separate Historical and Predicted report pages.
- Bookmarks with predefined slicer states.
- A custom navigation experience.
Could you clarify whether your requirement is:
- The visuals should show the correct default period, or
- The date slicer itself must automatically change its selected value?
That will help determine the best approach.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.
Hi g-zakkour
We wanted to check whether you had a chance to review the solutions shared by Omkar_1712 to help resolve the issue. We hope the information provided helps clarify the question. If you have any further queries, please feel free to contact the Microsoft Fabric community.
Thanks
Srikanth Cheri
CST team.Hi g-zakkour
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Thank you.
