Scott White on 02 Oct 2018 22:18:32
I know I can change my data to be reflected in UTC but then i suddenly show, for example, Invoices paid Septmeber 30th as being paid in October. this is so wrong!
You simply need to change PBI where date slicers are reflecting local time and not UTC. I cannot display all of our financial data improperly (as UTC).
- Comments (10)
RE: Fix Releative Date Slicer / UTC issue.
This is a big problem for us too. Please fix.
Currently, if we want to filter for the last "1" day and the local time is past 5pm, it returns us the same date as today! I'm guessing this is because we are in PST (with daylight savings).
RE: Fix Releative Date Slicer / UTC issue.
This is killing me. I've spent 3 days researching and trying to find a solution. What's the point trying to build a dashboard to show you real-time data but having the relative date +X hours different? My dashboards and reports are so beautiful......until 6PM.
RE: Fix Releative Date Slicer / UTC issue.
A silly problem for a nice product like Power BI.....please fix it or give the option to pick the time (UTC/server time)....
RE: Fix Releative Date Slicer / UTC issue.
This is still a massive issue for us. Please fix it.
RE: Fix Releative Date Slicer / UTC issue.
Setting the Power BI Service to local time is required. When connected to an SSAS live connection, a DAX formula can't be used as a work around.
RE: Fix Releative Date Slicer / UTC issue.
I do not believe that the comment/formula below will work correctly in most circumstances.
"UTC Time = IF(hour(NOW () ) < 11,[Date]-1,[Date])"
Reason being is the the relative dates for which to compare are calculated on the service before being compared to your data. For example, assuming UTC is ahead of your local time zone, the relative filter "Last Month (Calendar)" would prematurely flip over to looking at next month's data. The suggested formula approach could only fix the data for a particular relative time frame at best. This issue is exclusively on the service and can only be fixed by Microsoft. Truly, is a bug fix request and not a feature enhancement.
Please see the main idea that has the most votes so far:
https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/32123752-power-bi-service-recognize-local-time-zone-for-tod
RE: Fix Releative Date Slicer / UTC issue.
ok, I did a work around to the bug by adding this column (I am in AEST daylight savings):
UTC Time = IF(hour(NOW () ) < 11,[Date]-1,[Date])
And using this column to do the relative date slicer on.
RE: Fix Releative Date Slicer / UTC issue.
are there any work arounds in the interim?
RE: Fix Releative Date Slicer / UTC issue.
Yes, please fix!
RE: Fix Releative Date Slicer / UTC issue.
This should be taken on priority.