Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
I have a datatable from a SQL database with a local datetime column [DeliveryDateTime] that I need to join to other tables with UTC times.
I am using a Custom Column with the formula:
DateTimeZoneLocal = DateTimeZone.From([DeliveryDateTime])
When I add this step, I get a result that treats [DeliveryDateTime] as a UTC time:
which is not what the documentation describes.
If I add another Custom column step, either before or after the DateTimeZone.From step, suddenly the DateTimeZone.From starts assigning the local timezone.
Added column:
Custom= DateTime.AddZone([DeliveryDateTime], -11) (arbitrary datetimezone function, offset doesn't matter, before or after the From function doesn't matter)
Result:
If I remove the Custom column in another step, the DateTimeZoneLocal resets back to UTC (+0).
Can anyone else recreate this behavior? Is there any way to describe this except as a bug?
Hey @mr_fnord ,
I think you have to put the "cultural" parameter for the DateTimeZone.From function:
DateTimeZoneLocal = DateTimeZone.From([DeliveryDateTime], "en-US")
Otherwise Power Query doesn't know which local date this is.
Adding a culture works, but why the inconsistent behavior based on other datetimezone functions?
User | Count |
---|---|
103 | |
90 | |
78 | |
72 | |
68 |
User | Count |
---|---|
108 | |
96 | |
95 | |
74 | |
71 |