Slicer based on Relative pre-checked value is not updating correctly in desktop or service

[Anonymous]

Datasource: 2016 SSAS multidimensional cube

Issue: I have a slicer based on a relative date field in the date dimension.  The field value is the date unless today or yesterday, in which case "Current Date" or "Previous Date" is represented.  I published the report with "Current Date" selected but am finding the next day, when pulling up the report, although "Current Date" is what is showing in the slicer view, it is actually the previous value that is selected.  Both the key and date are the same in the cube so I don't think that Power BI is working with the MUN from the cube. Once I view the available values in the slicer the display updates to show "Previous Date".  It seems as though the slicer is holding on the value based on position in the list versus the actual value?  I'll add that the slicer is set to allow multi-select, with the select all option enabled.  Has anyone else run into this?  I wish power BI would come out with a relative date slicer that could be customized for fiscal year.

[AncaZ]

I have a similar issue with two kinds of slicer:

- the normal date slicer, set to "after" instead of "between". When I go to the report the next day, the maximum date is not updated. So if I want to change the date to yesterday, I can't. 

- a custom date slicer with relative dates: Today, Yesterday, Past week etc., for which I used DAX. This has the same problem: even if I go to the report two days later, the "Today" will still be stuck to the last time I published the report.

These issues come up in the Service, but all works fine on Desktop. It's the same when the report is based on direct query or imported data.

Has anyone encountered this problem and found a solution?

[PaulDBrown]

A bit of a long shot, but have you tried the refresh option in the report in the service?

[AncaZ]

Thank you for this suggestion! It solved another issue that I had :). But not this one unfortunatelly. I refreshed everything I could think of: data, page, visuals. It still doesn't work. I tried with a dashboard (with direct query from SQL) that I had published a few weeks ago and "yesterday" is 22 Oct. no matter what I do.

[PaulDBrown]

I take it you do have a date table with unique continuous dates?

[AncaZ]

When I tried with the slicer with the "After" date, I used a table with unique, continuous dates, yes. For the second option, the one with custom relative dates, the dates weren't unique. I created a table using a formula like this one:

Relative dates =

VAR yesterday = TODAY() - 1

VAR 7_days_ago = TODAY() - 7

RETURN UNION(

ADDCOLUMNS(FILTER('Calendar',[Date] = yesterday),"Data ref","Yesterday","Order",2),

ADDCOLUMNS(FILTER('Calendar',[Date] = 7_days_ago),"Data ref","7 days ago","Order",1),

ADDCOLUMNS('Calendar', "Data ref", "Custom...", "Order", 3))

I linked this table to my date table and used "Data ref" for the slicer. When choosing "Custom..." it's supposed to show a date slicer. So my Relative dates table contains the "Yesterday" and "7 days ago" dates twice, because they repeat for the "Custom" option. 

[Anonymous]

@Anonymous 

Current power bi service only support UTC datetime, and power bi desktop uses your local pc time. Please check the time gap between your local time and UTC time see if that is the problem?

Paul Zheng _ Community Support Team
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

The definition of current date happens in the cube refresh each morning so I don't believe that is the issue.  Thanks for responding though!