Why would an embedded OmniScript fail to receive the parent AccountId when previewing the embedded component, and what must be configured?

Why would an embedded OmniScript fail to receive the parent AccountId when previewing the embedded component, and what must be configured?

• A. Different element names between parent and embedded Set Values
• B. A missing Navigation Element between parent and child OmniScript
• C. The LWC PubSub Message flag in the Set Values action of the parent has not been set
• D. Data mapping conflicts between parent and embedded OmniScripts

Answer: (C)

In OmniStudio, data sharing from a parent OmniScript to an embedded child relies on a PubSub channel. When the parent sets values, those values will only reach the embedded component if the Set Values action is configured to publish via the LWC PubSub mechanism. Enabling the LWC PubSub Message flag tells the system to broadcast the parent’s data (such as AccountId) to the embedded OmniScript, so the child can receive it during preview. If that flag isn’t set, the message isn’t published and the embedded component won’t obtain the AccountId. Other issues, like mismatched element names, missing navigation, or data mapping conflicts, can cause problems too, but the specific missing AccountId in this scenario is addressed by ensuring the PubSub message is enabled on the parent’s Set Values action.

In OmniStudio, data sharing from a parent OmniScript to an embedded child relies on a PubSub channel. When the parent sets values, those values will only reach the embedded component if the Set Values action is configured to publish via the LWC PubSub mechanism. Enabling the LWC PubSub Message flag tells the system to broadcast the parent’s data (such as AccountId) to the embedded OmniScript, so the child can receive it during preview. If that flag isn’t set, the message isn’t published and the embedded component won’t obtain the AccountId.

Other issues, like mismatched element names, missing navigation, or data mapping conflicts, can cause problems too, but the specific missing AccountId in this scenario is addressed by ensuring the PubSub message is enabled on the parent’s Set Values action.