Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
leigh_f
Frequent Visitor

time zone region updating to +0:00 when refreshed in the online environment

Hi There, 

 

I'm finding that my data is being converted to +0:00 when publishing it online. 

 

When working in the desktop app, 

The data is originating from an Australian Dynamics 365 system, through the dynamics connector. 

It was coming incorrectly originally which I resolved through the transformation below

= Table.TransformColumns(#"ColumnX",{{"Date", DateTimeZone.ToLocal, type datetimezone}})

 

In addition I changed the desktop locale region to be australian to get the dates to update correctly. 

This worked brining the times and dates to be +8:00

 

When publishing it kept the correct times / dates originally, then on the first refresh, it restored back to the incorrect +0:00

 

I can't see any options in the online environment to change the region and it seems to pick up only +0:00

The main issue with this, is that it making a number of dates incorrect. 

 

Is there anyway to fix this in the online environment?

It seems like the region is always set to +0:00 which affects the local time. 

2 ACCEPTED SOLUTIONS

Cheers Ibendlin that link ended up being a partial solutuon to the issue but didn't show how to update the orignal column. 

ultimately I could not find a way to update the timezone for this query

= Table.TransformColumns(#"ColumnX",{{"Date", DateTimeZone.ToLocal, type datetimezone}})

What I could do as a work around instead was create a new column
= Table.AddColumn(#"Rename Column", "Date", each DateTimeZone.SwitchZone([#"Date"],10))

After this I needed to
Change the type to the date/time/timezone
Delete the original column 
Rename the new column to match the existing column's name 
This then rolled down to the following calculations. 

View solution in original post

2 REPLIES 2
lbendlin
Super User
Super User

Cheers Ibendlin that link ended up being a partial solutuon to the issue but didn't show how to update the orignal column. 

ultimately I could not find a way to update the timezone for this query

= Table.TransformColumns(#"ColumnX",{{"Date", DateTimeZone.ToLocal, type datetimezone}})

What I could do as a work around instead was create a new column
= Table.AddColumn(#"Rename Column", "Date", each DateTimeZone.SwitchZone([#"Date"],10))

After this I needed to
Change the type to the date/time/timezone
Delete the original column 
Rename the new column to match the existing column's name 
This then rolled down to the following calculations. 

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors