Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DateTime Conversion Functions Don't Preserve UTC Offset - Conflicting Documentation #1295

Open
FIMTooler opened this issue Feb 11, 2025 · 0 comments

Comments

@FIMTooler
Copy link

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".

image

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')

image

Results in the following output.
image

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.

image

I've tested Example 1 exactly as shown and get same output as the documentation.

image

image

Plan Type

Consumption

Steps to Reproduce the Bug or Issue

  1. Create new LogicApp.
  2. Initialize Variable with dateTime conversion function.
  3. Run logic app and view results.

Workflow JSON

Screenshots or Videos

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant