The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
Hi everyone, I checked many posts, tried various options, including unsuccessul attempts with ChatGPT so far. It seems like a common requirement, but not supported out of the box by Power BI. Thanks in advance for any help you can provide.
Requirements:
An alternative to a Between Date Slicer can be two individual date fields (From and To) if the same behavior can be achieved.
Any hint on how to achieve this? Thought that this basic feature in SSRS would be easy to replicate on Power BI, but apparently not! Thanks
Hi @erikbeauch ,
I tried to reproduce some of the requirements you need.
I create a table and a calculated column.
Table = CALENDAR(DATE(2023,1,1),TODAY())
column =
VAR _1 =
TODAY () - 1
RETURN
IF ( ( 'Table'[Date] ) <= _1, 1, BLANK () )
Next you can create a new measure and put it into Filter pane.
Measure =
VAR _1 =
TODAY () - 1
RETURN
IF ( MAX ( 'Table'[Date] ) <= _1, 1, BLANK () )
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Anonymous thanks for the suggestion. It would be acceptable if the users would clearly know to open the Filters pane and change the values there, but they are not savvy at all on this front and me must reproduce the SSRS version. So as a requirement, the slicer cannot be filtered, even from the pane. It's really about setting default values, without being limited to those in the selection.
@erikbeauch
I did a video some time back, pleas check it out: https://www.youtube.com/watch?v=KBEsPGxDxHM&pp=ygUWZGVmYXVsdCBkYXRlIGV4Y2VsZm9ydA%3D%3D
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
Thanks @Fowmy, the video is really well done. This is getting close to the requirements, but not entirely since it involves another filter than the Date Slicer and some resetting by the user. In the current use case, the goal is that the unique Date slicer will be used for user interactions. So it needs at all time to reflect the data range currently beeing displayed, instead of toggling between two slicers.