Here, timestamp is "triggerBody()?", the source time zone is UTC, the destination time zone is Eastern Standard Time, and the format is HH:mm.įor more information about this expression function, see the convertTimeZone. SourceTimeZone: The time zone the datetime is currently in.ĭestinationTimeZone: The time zone you want to convert your date to.įormat (optional): The format of the time zone you wish to convert your date to.įor example: convertTimeZone(triggerBody()?,'UTC','Eastern Standard Time','HH:mm') Timestamp: The datetime you wish to convert. You'll need to pass in the following ones:
A string that contains the time.Ĭonverts a string timestamp passed in from a source time zone to a target time zone Power Automate has an expression function for converting time zone.ĬonvertTimeZone(timestamp: string, sourceTimeZone: string, destinationTimeZone: string, format?: string) See the Notes below for ways to find the current time zone. Source time zone: The time zone that the datetime is currently in.ĭestination time zone: The time zone you want to convert your date to. The Convert time zone operation has a few required inputs:īase time: The datetime you wish to convert. Search for convert time zone and choose the Convert time zone operation. Power Automate has a built-in operation called Convert time zone. There are two ways to solve it - via an action or an expression. Some services use strictly UTC time to avoid confusion.
Each connector may use a different datetime format or time zone. It's because of services passing dates through in varying formats or time zones. Users may wish to convert the time zone (frequently in UTC) to their local time. When you're passing datetimes through triggers and actions in Microsoft Power Automate, users may find a datetime in the wrong time zone. This article provides a solution to an issue where you find a datetime in the wrong time zone.Īpplies to: Power Automate Original KB number: 4557244 Symptoms
0 kommentar(er)
