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.
As many users have commented, being able to set the default value for filters dynamically would be great. For example, date formats could let you set "greater than 12 months ago" and "less than 11 months ago". Or number formats could filter by "greater than" and "less than". Text formats could do the normal "starts with" or "contains". Etc.. This helps to define filters to be updated automatically as time passes and more data enters into the dataset that can't be identified/named during the development of the model.
Hello! This would be a great idea! But I'd like PBI to set the default date range for payroll. So based on today's date, I would like to set the end date to the previous Saturday, and the begin date to 7 or 14 or N days before the end date.
Aswell as a user being able to set a default it would be great if the developer could set these defaults in the model.
Imagine a company that provides reports to all of it outlets, where each outlet can only view its own relatable data (lets say sales). It would be beneficial for the developer to be able to set this in the model based on a users RLS profile. This kind of behaviour was available out of the box with SSRS and is a major step back for PBI in my opinion.
I have had two recent customer scenarios in which this feature would have invaluable:
- Customer had a daily report with a relative date slicer limited to last 30 days, but wanted the latest date to be selected by default - this is quite a common use case in my opinion.
- Customer had a report and wanted to have the flexibility to view sales data over any date range within the last 12 months, but wanted the default range to be the last 30 days. This could only be achieved with the use of two date slicers on the report - one being a relative date slicer covering the last 30 days and second being a slider with a date range covering the last year. Users have to clear the selection in the first slicer if they want to view sales over the wider date range in the second slicer.
Not sure if anyone brought it up yet. But would be great if Slicer has the option to choose newest date. This is because if you have dataset that is updated daily, it would be great if the slicer automatically choose the newest date every time its updated.
Hi Power BI team, can you provide an update of when you might be able to slot this in? This was added to idea board back in on 3/3//2015. That was over 7 years ago. What's the point of posting ideas that get pushed to the top of the vote list if you are just going to ignore them and do nothing?
Every client we work with has requested this, also it looks like thousands of other PowerBI users have requested this as well. This would be a great addition to PowerBI, sooner the better!!
Since it's the top idea on the "Microsoft Ideas" page for Power BI, maybe it will be implemented soon? Right now, the first of every month we have to go into every report and manually update the dates. Every new report, I still have to do this because we display reports last 12 calendar months (including the current month). The relative date slicer can't accommodate this logic.
since 2015 ? :D
Administrator on 10/20/2022 10:52:37 PM
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!