Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam OmniStudio Developer Topic 1 Question 70 Discussion

Actual exam question for Salesforce's OmniStudio Developer exam
Question #: 70
Topic #: 1
[All OmniStudio Developer Questions]

A customer sets up to LWC Omniscripts, one embedded into another. Account is set in a Set Values element in the parent Omniscript.

The AccountId set in the parent Omniscript is used to another Set Values element ContextAccountid in the embedded OmniScript. The embedded Omniscript is activated.

While previewing the OmniScript flow from the parent, it is found that Account is set correctly in the parent OmniScript. However. ContextAccountId in the embedded OmniScript is not set with the AccountId from parent Omniscript. On previewing the embedded OmniScript individually, it is found that ContextAccountId is set correctly.

What is the reason for this? Refer to the exhibit below.

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Diane
30 days ago
Wait, so the parent and embedded OmniScripts are like a pair of twins, but one of them just can't seem to remember their own name? Sounds like a case of identity crisis to me!
upvoted 0 times
Simona
10 days ago
User 1: Maybe the parent and embedded OmniScripts have the same element name?
upvoted 0 times
...
...
Cecilia
1 months ago
The passDataJSON flag in the parent OmniScript isn't configured correctly? Wow, that's a real head-scratcher. Looks like someone needs to brush up on their Omniscript knowledge.
upvoted 0 times
...
Dannie
1 months ago
Hold up, the LWC PubSub Message flag in the Set Values action of the parent hasn't been set? Seriously? That's like the first thing you check, right? *facepalm*
upvoted 0 times
Rosendo
16 hours ago
User1: Exactly. It's all about those small details that can make a big difference in the functionality of the OmniScripts.
upvoted 0 times
...
Gilma
13 days ago
User2: I know, right? It's such a basic step. That's probably why the ContextAccountId isn't getting set in the embedded OmniScript.
upvoted 0 times
...
Christoper
16 days ago
User1: Yeah, that's a rookie mistake. Always make sure to set the LWC PubSub Message flag in the parent OmniScript.
upvoted 0 times
...
...
Danilo
1 months ago
Wait, so the developer forgot to include a Navigation Element to pass data from the parent OmniScript? Talk about a rookie mistake. That's gotta be the reason.
upvoted 0 times
Lizbeth
10 days ago
C) The LWC PubSub Message flag in the Set Values action of the parent has not been set.
upvoted 0 times
...
Kathryn
15 days ago
B) A developer failed to include a Navigation Element to pass data from the parent OmniScript.
upvoted 0 times
...
Dick
23 days ago
C) The LWC PubSub Message flag in the Set Values action of the parent has not been set.
upvoted 0 times
...
Penney
1 months ago
B) A developer failed to include a Navigation Element to pass data from the parent OmniScript.
upvoted 0 times
...
Marjory
1 months ago
A) Both parent and embedded OmniScripts have the same element name for the Set values element.
upvoted 0 times
...
Willie
1 months ago
A) Both parent and embedded OmniScripts have the same element name for the Set values element.
upvoted 0 times
...
...
Queen
2 months ago
The parent and embedded OmniScripts have the same element name for the Set Values element? That's a bummer. Looks like a naming conflict to me.
upvoted 0 times
...
Melita
2 months ago
I believe option C could also be a possibility. The LWC PubSub Message flag might not have been set.
upvoted 0 times
...
Lawana
2 months ago
I agree with Paris. The developer might have missed including a Navigation Element.
upvoted 0 times
...
Paris
2 months ago
I think the reason for this issue could be option B.
upvoted 0 times
...

Save Cancel