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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Datetime string must m...
Power Automate
Unanswered

Datetime string must match ISO 8601 format.'.

(2) ShareShare
ReportReport
Posted on by 29
Flow error: Unable to process template language expressions in action 'Create_item' inputs at line '0' and column '0': 'In function 'convertTimeZone', the value provided for date time string '"5/5/25 8:15 AM"' was not valid. The datetime string must match ISO 8601 format.'.
 
Note: I followed an online tutorial to build my flow. I have no coding knowledge. I am having an issue with the date / time fields. I suspect the flow will also fail for a following number column (Duration) as well.
 
Flow function: An uploaded CSV file writes working hours to a sharepoint list. I have tried wrapping the split(item() expression in a format date time function, (as shown in the note above create item)  but that is not working. Any help would be greatly appreciated. I have spend hours trying to figure it out, but working with arrays is way beyond my knowledge base. 
 
 
Screen Shot 2025-05-29 at 11.45.44 PM.png
Screen Shot 2025-05-29 at 11.44.47 PM.png
Categories:
I have the same question (0)
  • Chriddle Profile Picture
    8,685 Super User 2026 Season 1 on at
    Although it doesn't conform to ISO 8601, your date format basically works. Don't split it.
    Your problem seems to be the double quotation marks. Simply remove them.
  • jj_AMS Profile Picture
    29 on at
    here is my updated expression: formatDateTime(item()?[1],'yyyy-MM-ddTHH:mm:ss')  The flow is still failing. The error now 
    Unable to process template language expressions in action 'Create_item' inputs at line '0' and column '0': 'The template language expression 'formatDateTime(item()?[1],'yyyy-MM-ddTHH:mm:ss')' cannot be evaluated because property '1' cannot be selected. Property selection is not supported on values of type 'String'. Please see https://aka.ms/logicexpressions for usage details.'.
     Any suggestions?
     
    Here is my list headings if that helps. At some point in trying to get this to work, I tried adjusting the content type of column 1 to text, that's why the time is missing. The CSV data resembles column 2.
     
    0                                        1               2            3
  • Chriddle Profile Picture
    8,685 Super User 2026 Season 1 on at
    formatDateTime(item()?[1],'yyyy-MM-ddTHH:mm:ss')
     
    You haven't split the item here.
  • tom_riha Profile Picture
    10,187 Most Valuable Professional on at
     
    you can use the expression parseDateTime(...) to convert date in any format into an ISO format as explained in this article.
     
     
    ----------------------------------------------------------------------------------
    Did the answer solve your problem? Please click "Does this answer your question" to help others find the solution too!
     
    You can find more of my solutions on my blog https://tomriha.com
  • jj_AMS Profile Picture
    29 on at
    I used copilot to try and help solve this. This was copilots suggestion 
     

    Thanks for testing that and sharing the result — this confirms that Power Automate is not able to parse the date string "5/5/25 8:15 AM" directly because it’s not in ISO 8601 format, and convertTimeZone only accepts ISO 8601.

    ✅ Best Solution: Preprocess the CSV to Convert Dates

    Since Power Automate doesn’t support custom date parsing formats like 'M/d/yy h:mm tt', the most reliable solution is to preprocess the CSV and convert the date strings into ISO 8601 format before using them in your flow.

    I can help you do this automatically by:

    1. Reading the uploaded CSV.
    2. Converting the "Clocked In" column to ISO 8601 format (yyyy-MM-ddTHH:mm:ss).
    3. Providing a cleaned CSV you can use in your flow.

    Copilot provided the following file for me. The flow worked with the file that was provided, but it kind of defeats the purpose of a flow that will process the default CSV file. I'm at a loss ??? 
     
    I'm attaching the cleaned file in hopes that someone will understand what the issue is.
     

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 641

#2
Vish WR Profile Picture

Vish WR 640

#3
Haque Profile Picture

Haque 495

Last 30 days Overall leaderboard