Free Plat-Dev-210 Exam Braindumps
Salesforce Certified OmniStudio Developer Questions 46–50 (page: 11)

Updated On: 10-Feb-2026

A developer has a requirement to create a child FlexCard that contain all of its parent FlexCard's records in a Datatable.

  1. {Records[0]}
  2. {Records}
  3. {Params records}
  4. {recordId}

Answer(s): B

Explanation:

The correct syntax for passing all of the parent FlexCard's records to a child FlexCard is {Records}, which represents an array of records. The other options are incorrect because they either use an invalid syntax or refer to a single record instead of an array of records.



An OmniScript updates data from one Salesforce record, but when it completes, only some of the data is updated in Salesforce. A DataRaptor Load saves the dat

  1. What error could cause this behavior?
    Choose 2 answers
  2. The fields that are not updated are read only in Salesforce.
  3. In the DataRaptor Load, in the Preview tab, the Record is from the wrong record type.
  4. The input JSON paths In the DataRaptor Load do not match the JSON from the OmniScript.
  5. ContextId is misspelled in the merge code that passes the Recordld to the DataRaptor

Answer(s): C,D

Explanation:

The input JSON paths In the DataRaptor Load must match the JSON from the OmniScript, otherwise the data will not be mapped correctly to the Salesforce fields. ContextId must be spelled correctly in the merge code that passes the Recordld to the DataRaptor, otherwise the DataRaptor will not be able to identify which record to update. The fields that are not updated are not necessarily read only in Salesforce, as they could be editable by other means. In the DataRaptor Load, in the Preview tab, the Record is from the wrong record type has no effect on updating data in Salesforce, as it is only used for testing purposes.



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?

  1. Show element if true
  2. Disable read only if true
  3. Set element to optional if false
  4. Set element to require if true

Answer(s): D

Explanation:

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 needs to retrieve data from an external system that stores policy dat

  1. The external system supports REST APIs to access and update the policies. Due to the volume of the policy data and peak hours of hours of business, calls to the REST APIs sometimes take longer than expected to response.
    The developer creates an Integration Procedure to retrieve the policy data for use in an OmniScript.
    Given the external system's known performance issues, which configuration should be used to implement the call to the external system?
    Choose 2 answers
  2. Set the Timeout property on the HTTP Action in the Integration Procedure
  3. Configure a Remote action with timeout settings of 120000
  4. Check the Chainable checkbox on the integration procedure Action in the OmniScript
  5. Check the Chain on Step Check on the HTTP Action in the Integration Procedure

Answer(s): A,D

Explanation:

Setting the Timeout property on the HTTP Action in the Integration Procedure allows the developer to specify how long to wait for a response from the external system before timing out. Checking the Chain on Step Check on the HTTP Action in the Integration Procedure allows the developer to chain multiple HTTP Actions together and execute them sequentially. Configuring a Remote action with timeout settings of 120000 is not necessary, as it is already done by default in OmniStudio. Checking the Chainable checkbox on the integration procedure Action in the OmniScript has no effect on calling an external system.



A developer needs to create a list of cases for an account in a single Datable in a FlexCard. Like the one shown below.



How can the developer configure the FlexCard to display the case records in this way?

  1. Enable the record Looping feature on the data table elements
  2. Select the Repeatable Mode property on the data table elements
  3. Enable the Repeat Records feature on the FlexCard Setup tab
  4. Disable the Repeat Record feature on the FlexCard setup tab

Answer(s): B

Explanation:

The Repeatable Mode property on the data table elements allows the developer to display multiple records in a single data table. The Repeat Records feature on the FlexCard Setup tab is used to display multiple FlexCards for each record in a data source. The Record Looping feature on the data table elements is used to iterate over a list of records and perform actions on each record. The Overwrite Target for all Null input checkbox on the Account id field is used to overwrite the existing value in the target object with null if the input value is null.



Viewing page 11 of 22
Viewing questions 51 - 55 out of 103 questions


Post your Comments and Discuss Salesforce Plat-Dev-210 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!