web

You’re offline. This is a read only version of the page.

News and Announcements icon

Power Platform CommunityForums Power Automate Time acting up from Po...

Power Automate

Suggested Answer

Time acting up from Power Automate to Dynamics 365

(2) Share

Report

Report

Posted on by Ibakordor Kharmih

11

I have a Power Automate flow that automatically adds cases to my dynamics crm. Currently there are issues where, the time format is mix matched. This is the second time that it is happening. What exactly is happening? Are there updates or so? The flow used to work fine.
In the image shared, the 2:30 AM should actually be 8:00 AM.

User's image

Categories:

I have the same question (0)

All responses Img

All responses (2)

Answers Img

Answers (0)

Sort by

Suggested answer

SpongYe 5,909 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!
Hi @Ibakordor Kharmih

The offset in your example is the clue: 8:00 AM > 2:30 AM is exactly 5 hours 30 minutes.
That is the offset between India Standard Time (IST, UTC+05:30) and UTC.

Power Automate is sending/storing the value as UTC, but you expected it to remain/display as IST/local time. In Dataverse/Dynamics 365, Date and Time columns can behave differently depending on whether the column is User local, Time zone independent, or Date only. “User local” values are adjusted for the user’s time zone, while “Time zone independent” values are displayed without conversion. Microsoft documents this behavior as part of Dataverse Date and Time column settings.

For your case, 8:00 AM IST being shown as 2:30 AM strongly suggests the flow is writing 08:00 as if it were UTC, or converting IST to UTC before saving, and the field/view is then showing the UTC-side value.

For IST, use something like this before writing to Dataverse:

convertTimeZone(<your time value>, 'India Standard Time', 'UTC')

If you have any questions or feedback, please let me know. Have a great day! 😊

-----------------------
SpongYe Power Platform Enthusiast [LinkedIn] | [Youtube| [My blog]

I love to share my knowledge and learn from others. If you find my posts helpful, please give them a thumbs up 👍 or mark them as a solution ✔️. You can also check out my blog [@S pongYe] for some cool solutions and insights. Feel free to connect with me on any of the platforms above. Cheers! 🍻

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(2)

Report
Copy link

Link copied!

Since the difference is exactly 5 hours 30 minutes, the most likely root cause is:

Power Automate / Dataverse is storing or reading the value as UTC,
while the business expects India Standard Time (IST).

I would start by examining the flow run history and the Dataverse DateTime column settings. In my experience, a precise 5:30 offset almost always points to a UTC

↔ IST conversion issue rather than a Microsoft platform update.

Was this reply helpful? Yes No

Join the conversation