Miguel Myers on 08 Oct 2024 05:00:00
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.
- Comments (418)
- Merged Idea (1)
RE: Epic idea: Apply filter selections automatically
I'm interested to hearing from my colleagues who are using Power BI and dealing with this issue. How are you able to overcome this? I worry about providing reports to clients, who are going to see out of date slicers and filters. Imagine if you opened booking.com and they defaulted to a date in 1999 for example. I think that's a good example of where Power BI is today.
RE: Epic idea: Apply filter selections automatically
Does the Power BI product team have any update when this will be deployed?
RE: Epic idea: Apply filter selections automatically
Thanks Miguel for updating this. This feature can't come soon enough.
RE: Epic idea: Apply filter selections automatically
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.
RE: Epic idea: Apply filter selections automatically
The scenario I'm working with is data-level language translations. I've got all the work done to swap out the column for the correct language based on a slicer/language table, but what I want is to be able to default that slicer to the USERCULTURE value in a DAX measure. That way when a es-ES user visits the page it automatically sets the filter and they do not have to choose a data-translation language. Metadata translations work fine via Translation Builder, but the data-level one seem to require the user specifically choosing a language. Having this feature completed would solve this issue I think.
RE: Epic idea: Apply filter selections automatically
Hello MSFT,Any update on this?We really need the capability of assigning default date on date slicers. User should be able to assign the start and end date before the report loads so that it will not requires a refresh when the value changes. It can be implement thru a measures that can be assigned when the slicer style is 'Between' .Another nice to have is a configuration when user selected a date range that is too narrow it should come up with a custom warning msg. For example i configured it that the date should always be 7 days apart, when users selected less than 7 it will give a warning base on configured message Regards,
RE: Epic idea: Apply filter selections automatically
To Power BI users everywhere: Please let Microsoft know the product is not really functional without slicers that can be preselected intelligently. For example, there is no way to preselect the most recent month (in a way that allows other date ranges to be selected). Yes there are ridiculous workarounds that take huge amounts of effort and don't really work.
RE: Epic idea: Apply filter selections automatically
Before I start this rant, I want you to know that I am a big fan of Power BI and its undisputed number one position for dashboarding/reporting solutions. The rate of change since the early inception days and Microsoft's commitment to providing a world class product is commendable. But then there is this ongoing issue of there not being an acceptable solution to have a default value for slicers. As others have posted, there are a number of workarounds, none of them, in my opinion hit the mark. I have used Microsoft's other reporting product, Reporting Services quite extensively, even before Power BI was around, and their ability to have a default value for a parameter based on a hard coded value or a value derived from a query is a simple, yet powerful solution. I cannot understand why Power BI does not have the same type of functionality, especially as both products are Microsoft.From a user perspective, they want to see current relevant data when they go into a dashboard without having to scroll through a list to find the latest month or have "Current Year" or "Current Month" as options. Sticky filters or Relative time filtering are also not really suitable especially if you want to see the latest month for which you have data. We might be in calendar month of today but the data in the dashboard might only become available during the course of the current month. Sod until that becomes available the slicer must default to the latest month, we have data for, i.e. last month, which changes to this month once that data is loaded later in the month.I also know there might be 3rd party visuals available which might address this issue, but surely, this is a big enough requirement and has been requested by many community members that justify that this be rolled out in the base Power BI offering.Pretty please.......
RE: Epic idea: Apply filter selections automatically
Any updates to share? Administrator message dated May 20, 2024 stated rummy
RE: Epic idea: Apply filter selections automatically
Slicers are so inconsistent, they are easily my least favorite part of Power BI. For instance, if a slicer exists on page with a value 1 selected AND on the same dimension one would add a filter with a value 2 (either through the Filter functionality or pushed through the URL when embedding the page in HTML), the slicer will still show the value 1 selected but will also show the value 2 (set through the filter) but visually unselected.In reality, both values are selected at this time because doing a SELECTEDVALUE() on the dimension returns nothing meaning both are selected.What kind of mixed message does this give to the user seeing this as well as end up with wrong data (due to both values being selected).Slicers urgently need to be overhauled to provide some consistency. This includes the ability to set a default value but also when done, it should UNSELECT the previously set value (which today it does not).Thanks