You need to sign in to do that
Don't have an account?
Alex 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
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
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
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