If a DataRaptor preview returns an empty response, what is the likely cause?

If a DataRaptor preview returns an empty response, what is the likely cause?

• A. The DataRaptor Action did not have the add response Ro Response JSON property set to true.
• B. A Response Action was not added to the integration Procedure.
• C. The Response cannot be previewed directly.
• D. The AccountId used for the preview is invalid.

Answer: (B)

In OmniStudio, the data returned by a DataRaptor is surfaced only when the Integration Procedure includes a Response Action that formats and sends that data back to the caller. A DataRaptor Action on its own retrieves or transforms data, but it doesn’t produce a client-facing response unless you wire its output into a Response Action. If the preview shows an empty result, it almost always means no Response Action was added to the Integration Procedure, so there’s nothing for the preview to return. To fix this, add a Response Action to the Procedure and map the DataRaptor’s output into the response structure. Ensure the Response Action is placed after the DataRaptor Action so it can package and return the data, and then run the preview again. The other options don’t explain the empty preview as consistently: issues like a specific property setting on the DataRaptor Action aren’t standard factors for preview output, and an invalid AccountId or inability to preview wouldn’t typically produce a blank response in the controlled preview environment.

In OmniStudio, the data returned by a DataRaptor is surfaced only when the Integration Procedure includes a Response Action that formats and sends that data back to the caller. A DataRaptor Action on its own retrieves or transforms data, but it doesn’t produce a client-facing response unless you wire its output into a Response Action. If the preview shows an empty result, it almost always means no Response Action was added to the Integration Procedure, so there’s nothing for the preview to return.

To fix this, add a Response Action to the Procedure and map the DataRaptor’s output into the response structure. Ensure the Response Action is placed after the DataRaptor Action so it can package and return the data, and then run the preview again. The other options don’t explain the empty preview as consistently: issues like a specific property setting on the DataRaptor Action aren’t standard factors for preview output, and an invalid AccountId or inability to preview wouldn’t typically produce a blank response in the controlled preview environment.