Answered

Sales Force Connector - Create a record error

(2) Share

Report

Posted on by ccb_101

Hello,

I have built a Power automate flow which has been working for months. Today I made a change to the flow, not related to the Sales Force Create Opportunity, and saved. After I saved, I now receive this error when my flow is used.

The 'inputs.parameters' of workflow operation 'Create_Opportunity' of type 'OpenApiConnection' is not valid. Error details: The API operation 'PostItem_V2' requires the property 'item/CloseDate' to be a string of maximum length '0' but is of length '10'.

Any ideas where I need to look to set the maximum length to not = 0. Opportunity close date is a required field so it can't be set to 0.

Thanks.

Categories:

Using connectors

All responses (4)

Answers (1)

Sort by

ccb_101 31 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi,

Even if you try to create a basic flow with a form and try to enter the close date manually the same error appears.

Does anyone have any ideas how to set the maximum length of this string as clearly it should NOT be 0.

Thanks.
ahmad_salameh 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Same here, I have a flow to upload attachments and it used to work perfectly, i started to have this error just yesterday.
ccb_101 31 on at

Like
a
(0)

Report
Copy link

Link copied!

Does anyone have an idea who manages the api parameter validation code? Because clearly this validation check is incorrect or was changed with a typo in it. This field should NOT have a validation check of 0 but should actually be 10 or a value higher.

Flow save failed with code 'OpenApiOperationParameterValidationFailed' and message 'Input parameter 'item' validation failed in workflow operation 'Create_record': The API operation 'Postitem_V2' requires the property 'item/CloseDate' to be a string of maximum length '0' but is of length '10'.'.
Verified answer

ccb_101 31 on at

Like
a
(0)

Report
Copy link

Link copied!

Just an update to say that the issue has been fixed by Microsoft. So the flow is working again.

See the comment from zachzepp in the below.
https://powerusers.microsoft.com/t5/Using-Connectors/Salesforce-Connector-Update-record-V3-throwing-strange-error/m-p/1946059#M17042