You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm unsure if this is a bug in the conversion functions or incorrect documentation. Possibly both as the functions do not honor specified formats with "K".
I've noticed that many of the datetime functions do not preserve UTC offset. Documentation HERE. The Return Value table indicates that there is no UTC offset which conflicts the default Format of "o" documented above that includes "K" for time zone information and clearly says "preserves time zone information".
Even when the format is specified instead of using the default "o", the UTC offset is not on the output.
Example: convertFromUtc(utcNow(), 'Pacific Standard Time','yyyy-MM-ddTHH:mm:ssK')
Results in the following output.
The Return Value table for convertTimeZone function does NOT include the same language "without the timezone UTC offset". However as seen in Example 1, the UTC offset is not included in the result.
I've tested Example 1 exactly as shown and get same output as the documentation.
Plan Type
Consumption
Steps to Reproduce the Bug or Issue
Create new LogicApp.
Initialize Variable with dateTime conversion function.
Run logic app and view results.
Workflow JSON
Screenshots or Videos
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the Bug
I'm unsure if this is a bug in the conversion functions or incorrect documentation. Possibly both as the functions do not honor specified formats with "K".
I've noticed that many of the datetime functions do not preserve UTC offset. Documentation HERE. The Return Value table indicates that there is no UTC offset which conflicts the default Format of "o" documented above that includes "K" for time zone information and clearly says "preserves time zone information".
Even when the format is specified instead of using the default "o", the UTC offset is not on the output.
Example: convertFromUtc(utcNow(), 'Pacific Standard Time','yyyy-MM-ddTHH:mm:ssK')
Results in the following output.

The Return Value table for convertTimeZone function does NOT include the same language "without the timezone UTC offset". However as seen in Example 1, the UTC offset is not included in the result.
I've tested Example 1 exactly as shown and get same output as the documentation.
Plan Type
Consumption
Steps to Reproduce the Bug or Issue
Workflow JSON
Screenshots or Videos
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: