Forum Discussion
Incorrect Time Zone setting at Power BI Service
Hi raymondwkmok
The Power BI service only operates in the UTC time zone, you need to adjust dates & times in DAX or Power Query.
There are lots of resources on this these few may help..
Dynamic time zone conversion using Power BI – The White Pages (unlimitedviz.com)
Power BI Service Time Differences and How to Fix It (linkedin.com)
Showing Current Time and Latest Refresh Time at Local Timezones in the Power BI Report - RADACAD
Hope this helps
Stuart
Hi raymondwkmok
The Power BI service only operates in the UTC time zone, you need to adjust dates & times in DAX or Power Query.
There are lots of resources on this these few may help..
Dynamic time zone conversion using Power BI – The White Pages (unlimitedviz.com)
Power BI Service Time Differences and How to Fix It (linkedin.com)
Showing Current Time and Latest Refresh Time at Local Timezones in the Power BI Report - RADACAD
Hope this helps
Stuart
The fact that this is still an issue in Power BI is absolutely laughable.
We have a report that was built in PBI Desktop, highly complex (has over 60 date & time columns + multiple calculated columns off the back of them) and only realised this was an issue once it was published to service and the dashboard went through it's first refresh - minusing 10 hours as the data is in AEST.
If there was a way to solve for this (i.e. apply a blanket rule you could apply aross all date & time columns in the dashboard to compensate the time difference) we would implement and continue with Power BI in our organisation, but to be told by Microsoft Support "just make a new calculated column for each" and "there is no other way" is utterly ridiculous response/resolution for an already data-intensive dashboard.
I sincerely hope Microsoft sees this and considers doing something about it. If my data in Dynamic365 is captured and presented correctly, it should be presenetd THE SAME when fed through PBI service - it is illogical to change the value from what it is/intended to be.
This specific case is now the basis of a discussion in our organisation of over 40,000 employees to move away from Power Platform (PBI specifically) back to Tableau as this was not an issue we faced using the same data sets. If an application captures data as:
02/11/2023 - 3:00pm
It should be presented as such, not manipulated, not require a custome column etc - it is a raw value which should be presenetd accordingly.