Jacek Power BI User on 03 Mar 2015 07:53:52
Allow a user to set the default value for a slicer or tile-by value on a page/dashboard, so that when the Power View page is opened for the first time, the default value is selected.
eg. If the page has a slicer for Year or Month, allow the user to configure the most recent Year or Month to be selected by default.
Administrator on 20 Oct 2022 22:52:37
Update 10/20/2022 - Update from Mo - we are working on this in the new year
Thanks for everyone's votes and comments. This is a feature on our backlog; however we cannot share a timeline at the moment.
It looks like many of the requests will be addressed by the new 'Sticky filters' capability. Now when you log out of Power BI and come back to a report, the same items will be selected as when you left. For those who're looking to have a 'last month' selection, the relative date slicer might help. Those with comments about currencies where having multiple selected makes the report meaningless - the report will load with whatever selection the author saved, so if you save it with one currency selected your users will see that by default. If there are scenarios that these features don't address, please let us know in your comments - if you are really specific it'll help us build the feature to work just the way you want! Thanks again!
- Comments (526)
- Merged Idea (15)
RE: Default Selected Slicer or Tile-By Value Configuration
So often it's necessary to open report with dynamic default slider filter. Usually, it's about period/time slicer.
So, would be great to create parameter "default value" for slicer visual. And as default value user could be set any aggregated measure from his data model
RE: Default Selected Slicer or Tile-By Value Configuration
A great thing would be to set the end date of a date slicer automatically to current date or end of current month.
For reports that are automatically refreshed daily this would improve handling a lot.
In certain reports i don‘t wan to use a relative date slicer but a from/to slicer always starting the same date (e.g 01/01/2018) and end date is always moving automatically to current date today or to end of current month.
RE: Default Selected Slicer or Tile-By Value Configuration
Allow Slicers to be preset based on defined criteria (i.e. DAX formula or other developer input).
For example, a dashboard that displays KPI data based on the current week end date. On displaying the dashboard the screen should default to the current end date with the user having the optional ability to set the date slicer for previous weeks.
At a stretch you could have a button with a bookmark action to run some DAX that could set the date slicer to the latest end date.
Taking this further you could also reverse and forward the slicer to the next selection (via DAX or other command/action).
RE: Default Selected Slicer or Tile-By Value Configuration
A workaround for this issue with easy UX:
https://www.linkedin.com/pulse/custom-range-date-slicer-power-bi-dynamic-defaults-more-a%C5%9F%C4%B1ro%C4%9Flu/
RE: Default Selected Slicer or Tile-By Value Configuration
Having date slicers default to a date automatically based on a measure. As an example:
Default Date = UTCNOW() - (4/24) ->bringing it to todays date but in EST time zone.
The idea is to be able to use the calendar select feature of date range but have the start / end date be specified by two measures.
The current solution of using text like yesterday or today in place of date is creating problems. Since clients like to use a calender view to set the date.
RE: Default Selected Slicer or Tile-By Value Configuration
Here is a use case where being able to set a default value is really vital.
I have a report which is used by multiple people, each of whom needs to see management information for their environment(s). They have a drop-down (slicer) to allow them to pick an environment. Currently, I'm using row level security to ensure they see their own environments, and not each others'. However... the default environment (the last value I saved with) is shown to ALL users when they access the table. This is a security issue and a usability issue, as the users are super confused about why they are seeing an environment which isn't theirs- and they are being shown information that they do not have permissions to see! Once they select a value, then they can only see their data, but it's not good.
My plan was to just select all environments each time before I save (then by default they see aggregated data relating to just their environments)- but that requires me to allow multiple select, which doesn't make sense for the users or the interface.
I really don't want to have to create a "dummy default environment" as it will make it much, much harder to manage all my aggregation measures (I have to report on matters relating to all environments in a given business line, as well as on individual environments).