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 (523)
- Merged Idea (15)
RE: Default Selected Slicer or Tile-By Value Configuration
We need this to be programmable. Maybe have a DAX measure that returns the default value that should be selected. As an example, select the user's department by default, while still leaving the other selections available.
RE: Default Selected Slicer or Tile-By Value Configuration
Can you please also add the forced selection like currently available in chiclet slicer, its very much needed? Thanks in advance for help.
RE: Default Selected Slicer or Tile-By Value Configuration
Voting for this idea because I need to show data from first day of current month till the last date in the date field by default and also provide users with ability to move left circle to see historical dates. I'm using slicer with "between" option and I can't set first day of the month (or today () , for example) as a date for left circle by default.
RE: Default Selected Slicer or Tile-By Value Configuration
How many votes are required for an idea to approved ?
RE: Default Selected Slicer or Tile-By Value Configuration
Upvote. This should be standard functionality
RE: Default Selected Slicer or Tile-By Value Configuration
Any update?
RE: Default Selected Slicer or Tile-By Value Configuration
Anyone from Microsoft can comment on the status?
RE: Default Selected Slicer or Tile-By Value Configuration
Can Power Bi give an update on the status of this? I need a report to default to current year and current pay period, out of a query that is generated every week. Right now the report consumers need to select the year and current period. The VP's want it to default to current on both hence the request. So right now for instance we would want year 2020, and period 22 selected in the slicer.
RE: Default Selected Slicer or Tile-By Value Configuration
I would really like to see the ability to use a start and end date slicer, but that can default to a preselected date range such as the current month to date. Many users would still like the ability to view any date range, even if the report opens with the current month. Right now, it's not possible to have it both ways.
RE: Default Selected Slicer or Tile-By Value Configuration
Has 3k votes and the last update on this is more than 2 years old! This feature is really needed, there is almost no project where this doesn't come up. This should work just like in SSRS, being able to set a default value for the slicer when the user opens the report (current year, current month, etc.).
And no, having another column in which I put "Current year" and use that as a slicer could be a workaround, but definitely nowhere near what the user wants to use, and let's be honest, it's not really a good solution on both ends: being the dev who needs to implement it or the user who need to understand why such a basic (reporting) functionality isn't implemented yet :(.