Power Platform Community Forum Thread Details

I have a list which includes several date/time fields. When I bring these into a Flow, the time is always 4 hours later than local time (e.g.: if the time stored in the field is 5:00 PM EST, it renders as 9:00 PM). I've checked the time zone in Regional Settings and it's set correctly. I double-checked the values stored in the fields. It's not UTC (that would be 4 hours 'fast' - show as 1:00 PM instead of 5:00 PM). I noticed this some time ago and worked around it by using the "addHours" function with a negative number of hours, but doing that in every Flow is going to be a royal pain in the you-know-what.

Can someone explain why this happens and if there is a programmatic way to get the correct time in my Flows?

EDIT: I finally took the time to fully read this page and discovered that Flow "reads" all times as UTC. Further, the "Convert Time" action is a much easier method than using the addHours expression/function. It's still kind of a pain that each individual timestamp needs to be converted individually, but there's a workable solution. We have some processes with 6 or 8 different deadlines or other date/time fields involved, so it'll be tedious, but we don't have much of a choice.

Categories:

Building flows