An OmniScript displays data from an API using an Integration Procedure, but some of the...

When an OmniScript receives incomplete data from an Integration Procedure, the issue is typically in Response JSON path mapping or naming mismatches.

A. The missing data is trimmed in the Integration Procedure Action Response JSON Path – If the Response JSON Path only points to part of the structure, any nested or unrelated values are excluded from the output.

B. The element name for the missing data does not match the JSON node key in the Integration Procedure Response – OmniScript expects a matching node name to bind the data to UI elements. If the key doesn’t match, that field will appear blank.

Incorrect Options:

C. Preview Input Parameters are only for testing in the Integration Procedure editor; they don’t affect runtime execution.

D. Even if the JSON from the Integration Procedure Action is different from the original IP input, it would cause a failure or unexpected data, not necessarily missing specific values.

Salesforce OmniStudio → Integration Procedures → JSON Path and Data Binding