Allow Slicers to be preset based on defined criteria
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).
Jinu Alappatt commented
It will be great if we can have a search button on slicers and selects all of them which is filtered using search button as in Excel Filter. Currently the search button is on top of the filter and nothing has been selected based on it. We need to select them one by one after it is filtered.
A more general solution might be to set a slicer to default to the max or min value, so it would work with more than dates.
Yes please! I have a report that gets updated weekly, with weekly release data imported from Jira. The end users like to start viewing the dashboard with only the most current release data visible, but they want to be able to then adjust the sliders to compare to previous data. So the longest step in my publishing process each week is going through all the pages of the report, nudging up the bottom node on all the sliders so they only show the ones with the highest release number.
Peter Ivers commented
David, realize this is just one example, but here's how we solve the date issue. Our models have date dimensions with calculated fields of YearsAgo, MonthsAgo and DaysAgo, where for example DaysAgo=0 is today, 1 is yesterday, etc. The default slicer in your example would simply be WeeksAgo=0.
I'd even settle for being able to use a measure in a slicer.