7 Comments
Three years later and MSFT still pretending client time-zones are irrelevant 😟
Extending on this issue...
The below screenshot is from the Microsoft documentation regarding what time zone is used in a Dataflow refresh, depending on whether a scheduled refresh is setup. So many Power BI solutions do not use the scheduled refresh and rely on other methods to manage the refresh schedule, e.g. Power Automate. This means you're stuck with time zone issues.
[img]https://i.imgur.com/Us2odEV.png[/img]
To remedy this, and achieve what Roman is suggesting, why not allow for the 'default' time zone OUTSIDE of the scheduled refresh settings?
getTimezoneOffset()method in JavaScript does take daylight saving time (DST) into account, and would be a easy fix for Microsoft to return the same way as the USERPRINCIPALNAME() do.Then it also would be easy for all Power Bi report developers to adjust time without doing complex api calls towards other web servers to get this done.
Also strange thing that Microsoft is ignoring this question.
Yeah Microsoft, what are you doing, this is like basics.
Let me set the TimeOne of my tenancy for Fabric and Power BI.
- Status added:Needs Votes
- Would really like to have this set at the Fabric Capacity, or Fabric Workspace Level
