Epic idea: Apply filter selections automatically

[Miguel_Myers]

Imagine a world where report creators can automatically apply slicer and filter selections based on specific logic, revolutionizing data analysis and user experience. This innovative approach eliminates any need for complex workarounds, optimizes slicer functionality, and paves the way for more efficient and effective data reporting.

[anthony_taylor7]

Could we get a new format category (General/Selection controls/ DEFAULT VALUE / .) on slicers, which allows for a value/formula/based on another field. to define the default. Eg. default value = value in this field (CurrentFY = "FY2019/20"); if default value field doesn't match a value in the slicer list, no valid default. Relative date slicers don't work for financial years when they differ from the calendar year. We flag the Current Day/Week/Month/Financial Year time period with a column (physical/calculated/measure doesn't matter), and have a slicer be able to default to that value based on that "Current (time period)" field. The user may want to select another non-default item from the slicer, but it should default to the specified value when opened/reset. A filtered slicer doesn't help here, because it will limit the slicer selection to only the Current (time period). The only workaround for now is to change the slicer value each day/week/month/year, save and republish. In a controlled production environment requiring a Change Request to promote production changes, this is not feasible for such small, regular changes. Similarly this would help the default currency people, where there could be a different default for each region or even user, based on another column/measure/formula. Remember, we're just trying to make users' lives easier. Thanks for all your hard work on this product. It IS appreciated.

[szymon_grabowsk]

Hi Guys, Do you have plans to develop it? It would be really appreciated as now we have to change the slicer each time. The report was saved with "!" one, bus with row level security do not allow some users to see "1" - they should see only "2". When this option is implemented we can indicate with DAX what should be the one selected by default. Thanks, Regards, Szymon

[jtn2]

This is critical. The only workaround for now is to change the slicer value each day/week/month/year, save and republish. In a controlled production environment requiring a Change Request to promote production changes - too much operational overhead. Must address.

[davis1]

This is a critical update in my opinion.

[boniecka-grzela]

I would need to be able to default the slicer to a certain period, for example the prior period. I still need to have an option to select other periods as needed. The reason is that the previous period is needed 95% of the time, but the remaining 5% of the time they the user would look at other periods.

[braden-smith]

Yes, this idea is critical. For example there are some reports where we would love to default the department to that user's department automatically. Having the ability to dynamically change the default would solve this. Similar to how it works in SSRS, you can return the value you want to use in another data set. I foresee where in Power BI you could do something similar. We have attempted to use Row level security and work around it by basically populating a table with every single possible slicer value for every user and then just setting the default to "My Dept." or something like that...but it's not very salable as more users start.

[psastre]

I need to be able to default a date slicer to a "Current (time period)". And then give the user the ability to select another non-default item from the slicer, but it should default to the specified value when opened/reset. This is highly needed! Thanks!

[michael_fudge]

I need the ability to set a default relative date (e.g. the last 30days) but have the slicer sent to between. The relative date slicer does not work for many reports.

[pdelia1]

This is also a serious deficiency in being able to use RLS effectively. Right now a slicer will attempt to use a default value that has been filtered out by RLS (and thusly load no data into the report by default). That's ridiculous. Either Slicers need to correctly default to values they can actually utilize, or this could be implemented so that you could setup a DAX Measure that feeds a default slicer value based on what is available in RLS. There's a bunch of inelegant hacks around this right now that I would rather not implement.

[pbiideas1]

I would find it very useful in a number of reports to be able to have a default value in a date slicer set to be today's date.