Forum Discussion
Issue with Slicer Not Updating to Latest Order Date Upon Dashboard Refresh
- Anonymous2 years ago
Hi Praj8050 ,
Thanks for mussaenda's reply!
And Praj8050 , I did some test but I can't reproduce your problem. Perhaps you can try the following:
Assume this is your Sales table:Use this DAX to create a calculated table for slicer:
Calendar = VAR _MIN = CALCULATE(MIN('Sales'[Date]), ALL(Sales)) RETURN CALENDAR(_MIN, TODAY())
Create relationship:Then you can use the table Calendar to create slicer:
Every time you refresh, the date range in the slicer will always be updated to the range from the minimum date in your Sales table to today's date.
Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Had a similar issue with between slicer and I found the solution in a tutorial and worked for me.
The ideea is that when we create a between slicer in Power BI Desktop if we want to test it to see if is working properly we need not to touch it in desktop, but publish the report on service and test it there on the workspace. Once you select certain values in destop, for a between slicer, even if in the end you select all possible values, Power BI will hard code those values available on desktop and when you publish the report and deploy it to another environment, after refresh you will see the selection made in desktop. Power BI thinks that this is what you wanted to be selected by default, and you need to manually drag the slider to see the latest data.
The problem is that we need to be carefull when we made other developments in the future for this report, and not touch the between slicer, otherwise we need to deleted created again and only then to publish the report.
For me this solution worked.