A developer creates a Flexcard that displays a contact's mailing address and passes the contact's postal code to a child FlexCard.
When configuration text elements in the child FlexCard, what syntax should a developer use to refer to the contact's postal code?
Answer : D
The Params node contains the data that is passed from the parent FlexCard to the child FlexCard. The developer should use {Params.postalcode} to refer to the contact's postal code in the child FlexCard.
A developer is creating an OmniScript that provisions trail orgs to their customers. The following text block in the Omniscript uses a merge code to display the ID for the new trail org:

Answer : B
The correct syntax for merge codes in OmniScript is %%sNodeName%%, where NodeName is the name of the JSON node in the data source. The other options are either missing the s or using incorrect symbols.
In an OmnoScript, a developer needs to configure a Disclosure element to require user input only if the user already checked a Non-Disclosure Agreement Checkbox.
How should the developer configure the conditional view to meet this requirement?
Answer : D
Setting the element to require if true allows the developer to configure a Disclosure element to require user input only if a condition is met. In this case, the condition is that the user already checked a Non-Disclosure Agreement Checkbox. The other options are either incorrect or irrelevant for this requirement.
A developer configures a FlexCard with a Data Mapper data source that uses the params.id as an input. When the developer clicks "View Data" on the FlexCard, valid data displays. However, when the developer previews the layout, the FlexCard does not display.
What could cause this error?
Choose 2 answers
Answer : B, C
This scenario relates to FlexCard preview behavior and data mapping issues.
B . There is no Salesforce record for the FlexCard based on the RecordId in the layout's Test Data Source Settings -- If the test record does not exist, the FlexCard will not display any data during preview. This is a common setup mistake.
C . The Data Node field for the FlexCard is empty -- The Data Node field must be set correctly to match the JSON node where the expected data resides. If it is empty or incorrect, the FlexCard won't bind data to UI elements.
Incorrect Options:
A . Even if the RecordId is from a different record type, as long as the data structure aligns, it would still render; it's not a definitive reason for the card failing to display.
D . Attributes are not required to display field values directly; they are used for passing data between cards or from context, not for direct field rendering.
:
Salesforce OmniStudio FlexCard Data Source Setup & Troubleshooting
A developer needs to create DataRaptor to retrieve the name of an account for a contact.
Following best practices, how should a developer configure the extraction steps?
Answer : A
A DataRaptor Extract can retrieve data from multiple objects using extraction steps and JSON paths. However, if the data is from a single object, only one extraction step is needed. The Extract JSON Path can use dot notation to access related fields from that object, such as Contact.Account.Name.
A healthcare company wants to enable its subscribers to add, edit, or delete dependents related to their policy Community portal. The developer on the project decides to use an MniScript.
How should the developer configure the OmniScript to providethis functionality?
Answer : A
Which JSON from the DRGetAccountDetails action would display all six values correctly in the Omniscript structure shown?
BlkContacts is a Repeat Block.


Answer : A
From the OmniStudio OmniScript Documentation:
A Repeat Block (like BlkContacts) expects an array of objects.
Each item in the array must contain fields that exactly match the UI elements inside the block.
The parent JSON must include any top-level values used by individual input fields (like AccountName, AccountPhone).
Why the Other Options Are Incorrect:
B . Uses Contacts instead of BlkContacts, and is incomplete/malformed.
C . Repeats keys at the same level instead of using an array structure. This causes the data to overwrite and fail to display properly.
D . Uses incorrect keys like 'Name' and 'Phone' instead of expected 'ContactName' and 'ContactPhone', breaking field binding.
Salesforce OmniStudio Developer Guide OmniScript Repeat Blocks & Data JSON Structure
DataRaptor Extract Output Mapping JSON for OmniScripts