Unanswered

DATE FORMAT ISSUE IN POWER AUTOMATE FLOW ISO 8601

(0) Share

Report

Posted on by Jetlir93

Hi everyone,

I seem to have this problem out of nowhere in my flow, where apparently the date format is valid - but it is working fine sometimes, while sometimes it doesn't. Here's a picture of two steps, where the first one START DATE TIME is working fine, while the END DATE TIME is failing, while having the very same format as the one above!?

MicrosoftTeams-image (55).png

Categories:

Using flows

I have the same question (0)

All responses (6)

Answers (0)

Jetlir93 6 on at

Like (0)

Report
Copy link

Link copied!

fyi - I though the error was with the input time of 24h format, but I tried one with 13:00 and it also worked.

Was this reply helpful? Yes No
wskinnermctc 6,519 Moderator on at

Like (0)

Report
Copy link

Link copied!

~~I don't know where the Base Time is coming from, but it is not is ISO 8601 format.~~

~~2023-10-02-06:30 - Your Current Value~~

~~2023-10-02T06:30 - ISO 8601 Format~~

~~The dash '-' in your current format is not correct, it should have a 'T' to represent time.~~

~~You will need to change that source time so that it has a 'T' in place of the dash '-' before it can be converted by timezone.~~

After re-reading, I see that the one in the first is actually working in the yyyy-MM-dd-hh:mm format.

Hmmmmm let me look closer

Was this reply helpful? Yes No
wskinnermctc 6,519 Moderator on at

Like (0)

Report
Copy link

Link copied!

Can you show the settings of the Convert Time Zone before the flow is run? Like you are showing the outputs, but can you show edit view.

Was this reply helpful? Yes No
wskinnermctc 6,519 Moderator on at

Like (0)

Report
Copy link

Link copied!

I put the same time in a variable and it is working. I don't know why yours would be different?

FYI: I don't think you need to be using the formatstring "u" which adds a "Z" at the end of the dateTime.

If there is a "Z" at the end of the datetime then it is considered UTC timezone. You are converting to UTC-02 which would not be the same as UTC. So you do not want a "Z" at the end.

You probably want to use formatstring [s] Sortable date/time pattern which does not end in a "Z".

Was this reply helpful? Yes No
Jetlir93 6 on at

Like (0)

Report
Copy link

Link copied!

tried it, still does not work. It is only working whenever the input is in the afternoon, meaning in 12h format. I once tried with 13:00 and it also worked.

Was this reply helpful? Yes No
Matthy79 4,186 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Why can't you just use ISO 8601?

If this is not possible you will have to translate it to ISO 8601. You could use parseDateTime for it. In your example it would be:

parseDateTime('2023-10-02-16:00', '', 'yyyy-MM-dd-HH:mm')

Was this reply helpful? Yes No