PLAT-DEV-210 practice question 3 of 25
When launching an OmniScript from an action on a FlexCard, the OmniScript displays, but no Salesforce data is populated: Which two errors could cause this behavior? Choose 2 answers Choose 2 answers
Full set: 103 questionsThis behavior indicates a failure in passing the necessary record context from the FlexCard to the OmniScript's data-fetching mechanism.
1. (A) The Id Field in the FlexCard's action properties is responsible for passing the record's ID to the OmniScript. If this field is blank, the OmniScript launches without context. Consequently, the DataRaptor inside the OmniScript has no ID to use as a filter, so it returns no data.
2. (D) Even if the FlexCard sends the recordId, the OmniScript must correctly map it as an input for the DataRaptor. If the merge field for the filter value (e.g., %recordId%) is misspelled in the DataRaptor Action's Input Parameters, the DataRaptor receives a null value and cannot query for the correct records.
B. There is no active version of the Data Raptor Extract. While an inactive DataRaptor would also result in no data, options A and D describe more specific configuration errors related to the flow of data context, a common and nuanced failure point.
C. There is no active version of the OmniScript. This is incorrect because the question explicitly states that "the OmniScript displays." An OmniScript without an active version cannot be launched or rendered.
1. Salesforce OmniStudio Documentation, "FlexCard Actions": The configuration for launching an OmniScript from a FlexCard action requires specifying the context, typically by passing {recordId}. The documentation states, "To pass the record Id of the record the FlexCard is on, enter recordId." If this context-passing mechanism is not configured correctly (e.g., the Id Field is blank), the OmniScript will not receive the necessary identifier. (Reference: OmniStudio Documentation, Build a FlexCard, FlexCard Action Properties).
2. Salesforce OmniStudio Documentation, "OmniScript DataRaptor Extract Action": This documentation details the "Input Parameters" section for a DataRaptor Extract Action. It explains that you must map data from the OmniScript's data JSON to the DataRaptor. For example, mapping the Filter Value to %recordId% sends the context ID to the DataRaptor. A misspelling in this merge field breaks the mapping, causing the filter to fail. (Reference: OmniStudio Documentation, OmniScript Elements, DataRaptor Extract Action).
3. Salesforce OmniStudio Documentation, "Activate OmniStudio Components": This guide confirms that both OmniScripts and DataRaptors must have an active version to be executed in a runtime environment. This supports the reasoning that option C is impossible, as an inactive OmniScript would not display. (Reference: OmniStudio Documentation, OmniStudio Basics, Activate OmniStudio Components).
Keep practicing
Take the free PLAT-DEV-210 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other PLAT-DEV-210 practice questions
- Question 1A developer creates a DataRaptor Extract to retrieve data to pass to an external service.…
- Question 4A developer is creating a FlexCard for a new Community page. The FlexCard will display ca…
- Question 5A developer needs to use the COUNTIF function to process data entered by the user in an O…
- Question 6A developer is configuring the API URL in an HTTP Action element within an Integration pr…
- Question 7A developer needs to limit the output of a Data Mapper Extract to a maximum of one result…
- Question 8In a calculation procedure, what is required for the output of a calculation step to be u…
