Forum Discussion
Daylight saving malfunction with December release
Hi all,
Can't find this problem on the forum, please let me know if solved elsewhere.
We maintain a date table, pull through direct query to PowerBI.
As of the Dec release (automatic update for me, and manual for a colleague so we saw both options) I noticed that an hour was lost on the 1st of October 2017 (daylight saving australia). This has affected the month and the quarter measures (they all show up as 30/09/2017 11:00:00PM, instead of 1/10/2017 12:00;00AM, but fixes itself on Jan 2018. Very strange, the SQL data checked and even the powerbi query editor shows the date table is fine.
13 Replies
I can't reproduce your issue. But you may use Power Query to transform Daylight Saving Time. Please refer to articles below:
Solving DAX Time Zone Issue in Power BI
Daylight Saving Time And Time Zones In M
Regards,
Hi,
Thanks, it's not a normal timezone offset though.
Have tried to share a picture that simulates what i'm seeing below. See how just the one wrong day affects the month and quarter. Again, on the SQL data this is not happening, just when loading into powerbi desktop Dec version.
Guy
Hi gghylon,
Did you manage to find a solution to this? I've also encountered the same frustrating issue.
- That's so frustrating! I've encountered the same issue. I'm afraid the only fix is to downgrade back to November version. That's what I did.
Having this exact same issues with the April 2018 release.
The April date an hour is being added.
seems weird as april dates in other tables aren't affected.I'm finding the way issue when the report is published to the web.
the fix seems to be to go to the computer date time settings and switch off automatically adjust for daylight savings.
Having this exact same issues with the April 2018 release.
The April 2018 date an hour is being added.
seems weird as april dates in other tables aren't affected.I'm finding the way issue when the report is published to the web.
the fix seems to be to go to the computer date time settings and switch off automatically adjust for daylight saving.
I'm surprised this hasn't been fixed yet. Because the April daylight savings effectively adds an hour to the date, I performed the following slightly lengthy workaround:
- Use of an hour column based on the date key
- Creating a calculated column to replace the previously used date key column:
if hour = 1 then
date - 1/24
else date
More than happy to provide more details if the above explanation isn't helpful enough.
v-sihou-msft any update on this as we are having the same problem and it's quite embarrassing? Thanks
Having this exact same issues with the April 2018 release.
The April 2018 date an hour is being added.
seems weird as april dates in other tables aren't affected.I'm finding the same issue when the report is published to the web.
the fix seems to be to go to the computer date time settings and switch off automatically adjust for daylight savings.
when you refresh the report it seems to come good.
