function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Alex TMAlex TM 

Nullable fields missing from Mulesoft External Service

When we create an External Services with Mulesoft, fields we have marked as nullable are excluded from the External Service. This means they're not available in Flow builder to assign variables to.
 
Am I missing something? Obviously we don't want to send values for all variables all the time, so some fields need to be nullable. Could this be a genuine bug?
 
Here's a small part of the API spec in Mulesoft where using for the External Service

User-added image
SwethaSwetha (Salesforce Developers) 
HI Alex,
Your ask looks similar to https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000FWw70

Does the workaround in https://issues.salesforce.com/issue/a028c00000gAwK6AAK/external-service-sends-null-for-all-properties-when-it-should-not help?

Thank you
Alex TMAlex TM
Hi Swetha, this is not quite the same thing. That article and thread talks about null values being sent, whereas we can't send values at all, even though we want to! :D 
SwethaSwetha (Salesforce Developers) 
@Alex, Apologies, and thanks for clarifying.

If you look at the generated apex classes for the request and the response u will see the fields are not present so then they don’t turn up in the external service.

I'll update this thread as I find more details. Thanks