Unanswered

Input parameter must be stringdate

(0) Share

Report

Posted on by JL-14081053-0

I'm not quite sure how to fix this error. I have 2 sharepoint lists with date and time fields and im trying to create a record on the second sharepoint everytime the first list is updated. The dates need to be in UK date.This was working a few weeks ago but now I get the error:

The 'inputs.parameters' of workflow operation 'Create_item' of type 'OpenApiConnection' is not valid. Error details: Input parameter 'item/OData__x0041_TT3' is required to be of type 'String/date'. The runtime value '"26/05/2023"' to be converted doesn't have the expected format 'String/date'

I have tried adding the below to format it to ISO date and added it to the 'create item' but I still get the same error
formatDateTime(triggerBody()?['Received_Date'],'yyyy-MM-dd')

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

abm abm 32,865 Most Valuable Professional on at

Like (0)

Report

Hi @dinasoup

Generally when you see something with 'item/xxxxx' under the Create Item action step means someone has deleted that column. You sure you have a column called OData__x0041_TT3?

If you don't have that column anymore then try remove the current mapping of OData__x0041_TT3 and save the flow. If you can't save the flow then try adding the create item step again. It will refresh the fields under the newly added action step and you won't be able to see OData__x0041_TT3 field. Let me know how it goes?

Thanks

Was this reply helpful? Yes No
Chriddle 8,436 Super User 2025 Season 2 on at

Like (1)

Report

This error means that "26/05/2023" is not a date string that you can insert.

“26” is not a valid month number 😉

With that in mind, is triggerBody()?['Received_Date'] already broken?

If this seemed to work previously, you should double-check that the data the flow filled in is correct.

I recommend only working with ISO 8601 formatted date strings.

Was this reply helpful? Yes No
JL-14081053-0 on at

Like (1)

Report

Thank you all, recreating the create item step helped. seems like there was an old deleted column there somewhere that was causing the issue

Was this reply helpful? Yes No