Unanswered

Salesforce Connector - Update record (V3) throwing strange error

(2) Share

Report

Posted on by Community Power Pla...

Hi, I have a few flows doing updates in Salesforce in an integration. I use the Update record (V3) to make updates in Salesforce.

The connector looks like this:

Note that the Opportunity Close Date field is marked as Required, it is important.

So when I run the flows this happens:

Let's have a closer look at the error:

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

If I understand correctly the error says that this field only accepts string with a max length of '0' but, even assuming that the Date field is converted to string, it doesn't make sense to require it to be length 0.

Note that this is Standard Salesforce field, literally nothing in it can be changed, let alone the field type or the max length (which can't be changed anyway because the field type is Date).

Any guess?

Categories:

Using connectors

I have the same question (0)

All responses (9)

Answers (0)

schirls 6 on at

Like (1)

Report

We also just started seeing this error on a new flow despite having several working flows using this connector.

Was this reply helpful? Yes No
ccb_101 31 on at

Like (1)

Report

Hello,

I got the same error today in my flows. I'm using the Create Record action. I only ran into this issue when I saved my flow. Other flows which have had no modifications done are still working ok. So something, and I'm not sure what, is causing the date field to not be accepted.

So for the time being I reverted to a copy of the flow I took a few months back. So don't make modifications to your flow which warrants a save.

My issue is tracked here
https://powerusers.microsoft.com/t5/Using-Connectors/Sales-Force-Connector-Create-a-record-error/m-p/1937075#M16995

I believe the parameter validation check is broken and should not be set to 0.

Was this reply helpful? Yes No
dmytro_mews 4 on at

Like (1)

Report

By any chance have you found what is different between broken version and restored in those jsons? I don't have any export of this flow that started throwing same error, so thought maybe I can fix it in export.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

@dmytro_mews I tried modifying the JSON of the flow and roll back the version of the method from Patchitem_V3 to V2 (field OperationID). However Patchitem_V2 throws the same error, I don't know what else to modify at this point.

Was this reply helpful? Yes No
jeremy-richards 5 on at

Like (0)

Report

I have a flow using the Salesforce connector that this morning began erroring out with the same error without any new changes applied. With mine it errors for the Update Record to update a Service Appointment. I'm pulling the appointment to be updated in the previous step with a Get Records operation, so I'm using the same data that's already there and it's telling me it's invalid. I've tried changing up some options since then. So far haven't been able to come up with a workaround though.

Was this reply helpful? Yes No
joelzehring 208 on at

Like (0)

Report

We're encountering the same error on flows with Salesforce actions. Updating any flow in the solution (not just the flow with the Salesforce update action) and then exporting a new version of the solution appears to result in a similar validation error.

Was this reply helpful? Yes No
zachzepp 8 on at

Like (1)

Report

We worked directly with MS support on this on Friday. They reached out yesterday and said the rolled back the change and deployed a fix across all regions.

Was this reply helpful? Yes No
zachzepp 8 on at

Like (1)

Report

We worked directly with MS support on this on Friday. They reached out yesterday and said the rolled back the change and deployed a fix across all regions.

Was this reply helpful? Yes No
jeremy-richards 5 on at

Like (0)

Report

I can confirm that my flow is now functional again. Thank you for this update.

Was this reply helpful? Yes No