When launching an OmniScript from a FlexCard Action, the OmniScript displays but no Salesforce data populates. Which error is most likely responsible?

When launching an OmniScript from a FlexCard Action, the OmniScript displays but no Salesforce data populates. Which error is most likely responsible?

• A. There is no active version of the OmniScript.
• B. There is no active version of the DataRaptor Extract.
• C. The Id Field for Actions in the FlexCard is not configured with the correct Recordid.
• D. In the DataRaptor Extract Action, the Input Parameters Data Source is misspelled.

Answer: (C)

Passing the right record context from the FlexCard Action to the OmniScript is essential for populating Salesforce data. The Id field on the Action is what carries the Salesforce record’s identifier (RecordId) into the OmniScript, so the DataRaptor Extract can retrieve the exact record data to fill the fields. If that Id field isn’t configured with the correct RecordId, the OmniScript will open but has no valid record to query, so no Salesforce data gets populated. If the OmniScript had no active version, or the DataRaptor wasn’t active, or if the input source for the DataRaptor was misconfigured, you’d typically see a loading failure or errors rather than simply missing data while the UI appears. The key fix is ensuring the Action’s Id field passes the correct RecordId so the data layer knows which Salesforce record to fetch.

Passing the right record context from the FlexCard Action to the OmniScript is essential for populating Salesforce data. The Id field on the Action is what carries the Salesforce record’s identifier (RecordId) into the OmniScript, so the DataRaptor Extract can retrieve the exact record data to fill the fields. If that Id field isn’t configured with the correct RecordId, the OmniScript will open but has no valid record to query, so no Salesforce data gets populated.

If the OmniScript had no active version, or the DataRaptor wasn’t active, or if the input source for the DataRaptor was misconfigured, you’d typically see a loading failure or errors rather than simply missing data while the UI appears. The key fix is ensuring the Action’s Id field passes the correct RecordId so the data layer knows which Salesforce record to fetch.