Allow formatting datetimezone fields to user local timezone

[basson_christia]

Typically date & time information is available in UTC (if not then put it to UTC at source), you just want it rendered in the users' locale/time zone at reporting time. Adding an option to format datetimezone fields in the users' locale/time zone (based on the user account settings) would probably solve 90+% of requirements for rendering time zone information. Currently MS does not provide for showing offset information (or local time zone) as you only have date/time format options, but in the query editor you can set type to datetimezone which show offset info so it's clearly available - just the rendering that lacks. Not having this functionality is forcing people to resort to hacks like using DateTimeZone.AddZone () with hardcoded time offsets - not scalable where DST is involved. Current workarounds obviously only work as long as the viewer is in the designated time zone and does not scale across a global audience.

[vithalmaddala]

Its ridiculous that this isn't available in Power BI.

[cplath]

Here's a hacky workaround to handle offset with DST in the PBI service: https://community.powerbi.com/t5/Service/Handling-local-time-zone-with-Daylight-Savings-in-Power-BI/m-p/991812#M91044

[kris_herbison2]

Come on Microsoft, it is ridiculous that this is not available! Why can't the online server use the local time of the person running the report! Especially if the report is to be used in multiple timezone! Please get this fixed ASAP.

[justin_jackson]

Please implement!

[Shaun_Wilkinson]

Ridiculous this is still an issue - having to manually calculate offsets and then continually update those offsets to cater for daylight saving time or different regions.

[raj_rao1]

This functionality is sorely needed, especially when your PBI reports are used globally. Otherwise, what is the point of storing data with DatTime+Zone?

[ChristiaanB]

Noticed this today - https://learn.microsoft.com/en-nz/power-bi/connect-data/incremental-refresh-overview#current-date-an.... Supposedly 'sets' the time zone for service scheduled refresh... but still does NOT address global audience showing in their own local time zone. This needs to happen client side, not server side.