Incorrect parameter name used when invoking an external service operation from a flow
Last updated 2020-07-02 ·Reference W-7597071 ·Reported By 8 users
When the schema for an API is registered as an External Service in Salesforce, if an Apex reserved word is used as a parameter name in the schema, we re-name it to a non-reserved word in order to represent it as an Apex object. The External Service should still do callouts to the API using the original parameter name, but instead it is using the re-named non-reserved word in the callouts. So the callout is incorrectly sending a parameter that the API is not expecting (nor defined in the schema).
In the following example, "Map" is an Apex reserved word.
"description": "The parameter will be sent as z0Map not Map"
"description": "This is fine"
1, Create an External Service using a schema where any Apex reserved word is used as a parameter name.
2, Create a Flow and put the External Service Action in it.
3, Run the Flow.
No workarounds at this time.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.