Forum Discussion
Inconsistent Date Conversions
I've been going in circles trying to get my date/time values correct in my online Service reports, trying to get consistent results in the context of the automatic conversion of times to UTC standard.
I've established a measure called "Current_Start_Palm_Meas" that takes and UTCNOW() value and applies time zone (-5 h), daylight savings time (+1 h), and my company's shift schedule (7:00 AM to 7:00 PM or vice versa) adjustments to determine the DATETIME value that represents when the present shift started.
If I take this value and put it in a CARD visual (Blue), it correctly reports a value of 7:00 AM.
HOWEVER, if I use this value as the X-axis starting time in a LINE CHART visual (Yello), it takes that 7:00 AM value, treats it like a "local" datetime value, and shifts it to the UTC equivalent (11:00 AM, no Daylight Savings ).
Note, the Pink datapoint has a time coordinate of 11:30 AM (local time). It does NOT get adjusted in the LINE GRAPH visual.
Am I missing something? My current workaround to establish an "uncorrected" measure to counter Power BI's overcompensation.
4 Replies
Hi _Nick_
What I would recommend doing is to change your datetime values in power query. That way when the data is coming into your model, the date time format is already established to be what you expected to be and you're not having to use dax or calculated columns to create this. This can very often create some of the issues you are experiencing.
Here are details on how to change the date time in Power Query: Power BI – Did you know ALL Power BI Services Servers are in UTC? Now how to handle it for Dates & Times - FourMoo | Power BI | Data Analytics
