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 (19)
RE: Fix Releative Date Slicer / UTC issue.
MSFT - any updates on this? This is important functionality for global companies. Alternative solution require a lot of coding or maintaining multiple versions of the same report.
RE: Fix Releative Date Slicer / UTC issue.
Nearly 2023 and STILL this is an issue. Seriously? This issue makes using Metrics (Goals) nearly unusable since it messes with all my dates, history, etc.
RE: Fix Releative Date Slicer / UTC issue.
Jumping on this bandwagon as it is still an issue in 2022. This automatic conversion to UTC is simply not usable for the majority of user needs. Even more infuriating is that I can develop my reports in desktop, confirm all datapoints (including time stamps) and to see those time stamps break when published to end users. If I wanted to report out in UTC I would develop my reports as such. Microsoft, please fix this at the report level.
RE: Fix Releative Date Slicer / UTC issue.
Its surprising how a feature that seams to basic and important to accurate reporting is missing. There is so much garbage "solutions" online that claim to fix the issue but you CAN NOT change the time zone in power bi service for the use of slicers. Don't waste your time on false fixes, vote this issue! Please Microsoft fix this!
RE: Fix Releative Date Slicer / UTC issue.
This issue just renders the feature useless and misleading!
RE: Fix Releative Date Slicer / UTC issue.
Same here. OP posted on 10/2/2018. Now 11/26/2021! Ridiculous much the wait on something as fundamental as this? I think so. C'mon Microsoft... you want me to do it?
RE: Fix Releative Date Slicer / UTC issue.
Having to publish many of Power BI reports to a the Power BI service and Teams means having to add 10 hours to any dates/times. I have a card visual in many of the reports that displays the last data refresh time (Date.Time.LocaleNow()) but when it refreshes on the service it deems the UTC date/time as the local system date/time. Its a painful bug, please fix.
RE: Fix Releative Date Slicer / UTC issue.
Microsoft please get this fixed it
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).