web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / DATE FORMAT ISSUE IN P...
Power Automate
Unanswered

DATE FORMAT ISSUE IN POWER AUTOMATE FLOW ISO 8601

(0) ShareShare
ReportReport
Posted on by 6

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:
I have the same question (0)
  • Jetlir93 Profile Picture
    6 on at

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

     

  • wskinnermctc Profile Picture
    6,519 Moderator on at

    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

     

     

  • wskinnermctc Profile Picture
    6,519 Moderator on at

    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.

  • wskinnermctc Profile Picture
    6,519 Moderator on at

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

    wskinnermctc_1-1696017785251.png

     

    wskinnermctc_0-1696017757177.png

     

    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".

    wskinnermctc_0-1696018536073.png

     

  • Jetlir93 Profile Picture
    6 on at

    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. 

     

  • Matthy79 Profile Picture
    4,180 Super User 2024 Season 1 on at

    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')

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 522 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 364 Moderator

#3
abm abm Profile Picture

abm abm 243 Most Valuable Professional

Last 30 days Overall leaderboard