Power Platform Community Forum Thread Details

I have a Power Automate action that creates and approves a Time Entry based on some provided data. I am located in the timezone GMT -6, and when the flow creates a record for a Bookable Resource in the same timezone as me (the flow owner), it sets the start column time correctly. However, when I create a Time Entry for a Bookable Resource in a different time zone (such as GMT -8) it sets the start time to something else that does not appear to be a direct offset. For example, passing through a start time of 2025-01-01 08:00:00 with a UTC Time Zone Conversion Code of 11 (Saskatchewan GMT -6) will set the start time to 8am on my own record, but 4am for somebody in GMT -8 and 5am for somebody in GMT -7 which does not make sense to me. I am guessing I am just misunderstanding something about how Dataverse interprets time zones upon record creation. The start column on the Time Entry table is set to User Local, which would lead me to believe that passing through 2025-01-01 08:00:00 should be interpreted as 2am GMT -8, but that does not occur either (still sets it to 4/5am).

Test account in GMT -8:

My account in GMT -6:

Categories:

Microsoft Dataverse with Power Apps

Hi,

## Fix: Time Entry timezone in Power Automate/Dataverse

- Set Dataverse DateOnly columns to Time Zone Independent; DateTime columns that represent moments-in-time to User Local.

- From Power Apps to Flow: send UTC.

- In Power Apps:

- UTCDateTime: DateAdd(YourLocalDateTime, -TimeZoneOffset(YourLocalDateTime), Minutes)

- Pass UTCDateTime to Flow.

- In Power Automate when writing to User Local datetime:

- If input is local: convert to UTC

- Expression: utcNow() or convertTimeZone(triggerOutputs()?['body/YourLocal'], 'India Standard Time', 'UTC')

- If input already UTC: write directly.

- In Power Automate when writing to Time Zone Independent datetime:

- Do not convert; write the exact value as provided.

- If you only have local and need to keep local: use convertTimeZone(variables('localValue'), 'India Standard Time', 'India Standard Time') to keep same clock time.

- Validate with 3 checks:

- Store: value saved in Dataverse equals intended UTC.

- Render: user sees correct local time in model-driven app.

- Roundtrip: UTC -> local -> UTC returns original value within 1min.