Power Platform Community Forum Thread Details

Error: "OpenApiOperationParameterValidationFailed. The 'inputs.parameters' of workflow operation 'Create_item_-_add_to_master_list' of type 'OpenApiConnection' is not valid. Error details: The API operation 'PostItem' requires the property 'item/field_66' to be a string of maximum length '255' but is of length '439'."

My flow is running into the above error when it triggers the 'Create item' action which populates columns in a share a point list and it's doing that for multiple columns for the same reason/error. I have updated the respective columns from single line to multiple line text through the SharePoint site list settings; however, I am still getting the above error at every iteration of the flow.

For context, this flow uses a Qualtrics API to gather the collected data from the Qualtrics forms/survey that people fill out and then populates the entered data into respective columns in a SharePoint list.

Error 1.jpg

Error 2.jpg

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Power Automate Desktop

Hi,

This error typically occurs when the Create item action is still using the old SharePoint column definition, even though you've changed the column from Single line of text to Multiple lines of text.

A few things to try:

Refresh the SharePoint connection
- Remove and re-add the Create item action, or select the SharePoint list again. This forces Power Automate to retrieve the latest column metadata.
Verify the internal column
- The error references field_66, which is the internal SharePoint column name. Confirm that this is the column you changed and that there isn't another column with the same display name.
Check the actual data length
- Add a Compose action before Create item to output the value being written to field_66. If the output is 439 characters (or more), it confirms the flow is attempting to write a value longer than 255 characters.
Save and republish the flow
- After changing the SharePoint column type, save the flow and, if necessary, remove and recreate the Create item action so it refreshes the column schema.
If the flow was exported/imported
- Cached metadata can persist. Recreating the Create item action is often the quickest fix.

If the issue persists after recreating the action, I'd recommend checking whether the destination column is actually a Multiple lines of text column by creating a test item manually with more than 255 characters.

Could you also confirm:

Is field_66 definitely a Multiple lines of text column now?
Is the Create item action older than the SharePoint column change, or was it added afterward?
Does the error occur for every long-text column or only certain ones?