Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have a date column in my database table in UTC and I want to convert it to my local time (Eastern Time), taking into account daily saving.
I tried to do it using the following PowerQuery functions:
I also found some posts where people tried to do their own conversion.
Do the PowerQuery functions not handle the conversion correctly? I'm a bit confused as to why further calculations are needed.
The screenshot below shows the result after using the PowerQuery functions. It looks like the time offset changed from -4 hours to -5 hours at 6AM UTC or 2AM Eastern time.
When I do the conversion using "AT TIME ZONE" in SQL, the result is slightly different.
https://learn.microsoft.com/en-us/sql/t-sql/queries/at-time-zone-transact-sql?view=sql-server-ver16
Here it looks like the offset changed from -4 hours to -5 hours at 2AM UTC.
Which result is correct? The one in SQL or the one from PowerQuery?
Please see this video for one way to handle DST. Note that it works in desktop but not in the service.
(7) An easy way to handle Daylight Savings Time in Power Query - YouTube
Pat
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
10 | |
8 | |
6 | |
6 | |
6 |