OmniStudio-Developer Salesforce Certified Omnistudio Developer (Plat-Dev-210) Questions and Answers

According to the Salesforce OmniStudio DataRaptor documentation, specifically under DataRaptor Load Best Practices and Common Issues:

A. “The Input JSON paths in the Data Mapper Load do not match the JSON sent from the OmniScript.”This is a common configuration issue. If the paths between the OmniScript ' s structure and the DataRaptor Load mapping are mismatched, fields may not map correctly, resulting in partial updates or no updates.

B. “The fields that are not updated are read-only in Salesforce.”If a field is Read-Only at the field-level security (FLS) or object schema, DataRaptor Load will not be able to write to it, which explains why only some data is updated.

Incorrect Options:

C. The RecordId from the wrong record type would typically cause a complete failure, not a partial update.

D. A misspelled ContextId could prevent data from being linked correctly, but this is less likely to cause partial field-level issues, and more likely to affect record association.

Salesforce OmniStudio Developer Guide → DataRaptor Load → Troubleshooting

Salesforce Help Documentation: OmniStudio DataRaptor Best Practices

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.

 The merge code syntax for passing data from a DataRaptor Extract Action to an HTTP Action is %DataRaptorName: NodeName%. In this case, it is %DRReadCase: CaseNumber%.

A DataRaptor Turbo Extract is a simplified version of a DataRaptor Extract that can retrieve data from a single object without changing the structure of the output data. It is easier to configure because it does not require defining extraction steps or JSON paths. It also has better performance at runtime because it uses a native query engine instead of a custom one

The child OmniScript must receive specific nodes from the parent OmniScript’s data JSON, so the developer should pass them through Additional Input key/value pairs on the child OmniScript element. Additional Input is used to pass named values into an action or embedded component when the child process needs specific data from the current script context. ContextId would pass only a record identifier, not full Address and Contact JSON nodes. PreFill is used to populate data into an OmniScript, but the question asks which property on the child OmniScript element should be used to pass parent nodes. LWC Component Override is unrelated because it replaces rendering behavior rather than mapping parent script data. Therefore, Additional Input is the correct configuration.

================

Updating Salesforce data from an OmniScript requires a write operation, so the correct tool is a Data Mapper Load. A Data Mapper Extract reads data from Salesforce; it cannot update the Contact record. A Data Mapper Transform only reshapes data between formats and does not perform the Salesforce database update. The Data Mapper Load should include the Contact identifier and the new Phone value so Salesforce can update the correct record. When upsert behavior is needed, the appropriate field mapping must identify the key used to determine whether the record already exists. The question asks specifically about changing a Contact phone number from an OmniScript, so the correct configuration is a Data Mapper Load with the RecordId/key and updated phone value.

================

The best available answer is A, but the wording is not perfect. The safe testing pattern is to avoid changing the published cache configuration used by production users. Changing Cache Duration to 0 or disabling the Cache property would alter runtime behavior for everyone using that active Integration Procedure. Changing Type/SubType is also a bad workaround because it changes the component identity and can break callers. A throwaway test input is the least disruptive option because it lets the developer create an isolated request path for testing rather than clearing or disabling shared production cache. In a real implementation, the test value must affect the effective cache signature; if an explicit Cache Key Property is configured and the throwaway value is outside that key, it will not bypass the cached entry.

================

According to the Integration Procedure Actions page, a Remote Action can use a function in an Additional Output value field or in a Remote Options value field. According to the Response Actions page, a Response Action can use a function in an Additional Input value field.

The correct best practice is to use one Data Mapper Load configured for the related object mappings. Salesforce documentation explains that Data Mapper Load supports updates to multiple Salesforce objects and displays separate mapping tabs for each target object. It also documents Multiple Related Object Loads, or Link Mappings, for propagating data between related objects during a load sequence. This avoids unnecessary multiple sequential Data Mapper Load Actions and keeps the update logic declarative, maintainable, and transactionally cleaner. A Remote Action with Apex should only be used when declarative mapping cannot satisfy the requirement. A Salesforce REST API HTTP Action is also unnecessary because the operation is inside Salesforce and OmniStudio already provides Data Mapper Load for this exact use case.

================

Navigation button labels such as Next are controlled through OmniScript setup-level label mapping/custom label configuration, not by editing each Step element or creating Navigate Actions. The Next button is part of the OmniScript framework navigation, so changing it globally for the script belongs in the setup configuration where element names and labels can be mapped. A Navigate Action is used to navigate to another page or component; it is not the framework Next button. LWC Component Override is for replacing component rendering behavior with a custom LWC, which is excessive and incorrect for a simple label change. Salesforce documentation describes OmniScript setup configuration and custom label references for OmniScript properties, supporting the setup-label approach.

A Data Mapper Transform is used to restructure input JSON into the output JSON format required by a target system. Since the target requires a nested array of objects, the developer must map the source value into the correct nested target path so the Data Mapper output structure creates the ContactDetails array and Phone object. A flat direct mapping does not describe the required parent array and child object structure. A Formula is not required just to place an existing source value into a nested output structure; formulas are used when the value itself must be calculated or transformed. Mapping to the root node would lose the required ContactDetails and Phone hierarchy. The correct method is nested target path mapping.

================

The best practice for configuring the Input JSON for a DataRaptor Load is to copy the Input JSON from the OmniScript {Data} modal. This ensures that the Input JSON matches the data structure and format of the OmniScript data. The DataRaptor Action Debug node may not have the same data as the OmniScript data, and building the Input JSON node by node in an editor or in the DataRaptor Designer may introduce errors or inconsistencies.

When testing a FlexCard data source in the designer, the developer must provide valid runtime values for context variables so the configured Integration Procedure can execute as it would at runtime. In this scenario, that means manually entering a valid Context ID, such as an Account record ID, in the Setup or Test Data Source settings and then viewing the returned data. Without a valid context value, the Integration Procedure may not receive the input required to query Account, Opportunity, and Case data. Option C is important inside the Integration Procedure design, but the question asks about testing the FlexCard’s data configuration in the designer. Option B is not generally required for SOQL. Option D is a design choice, not the key testing step.

The strongest listed choice is a Try-Catch Block, but the real implementation must also use Rollback On Error in the Integration Procedure configuration. Salesforce’s OmniStudio training states that Rollback On Error commits database changes only if the entire transaction completes successfully; otherwise, intermediate database changes are rolled back. A Try-Catch Block is used to run steps and catch failures, and with failure handling configured correctly, the failed block can return a controlled error response. A generic Group element only organizes or conditionally runs steps; it does not provide rollback by itself. Chainable processing intentionally splits work into separate transactions, which is the opposite of the requirement. Continue on Error only addresses Data Mapper behavior, not full transaction integrity.

================

 Option D is the correct way to configure Additional input to send exactly the same data as Input Data. The Additional input should have the same key/value pairs as Input Data, and the value should be set to {{InputData.key}} for each key. This will pass the value of Input Data for each key to Additional input.

Conditional Rendering is best when only one element, or a small number of elements, must be hidden or shown based on simple data logic. For example, if one field, label, icon, or block depends on a single Boolean or status value, a rendering condition is more efficient and easier to maintain than creating another FlexCard State. States are better when the card must switch to a substantially different layout or when many elements change together. Option D describes a state-level use case, not a single-element rendering condition. Option A is wrong because no condition is needed if the element is always visible. Option B is not the deciding factor; repeaters can contain conditional elements, but the reason is still the simplicity of the condition.

================

A DataRaptor Transform can be used to transform data from one format to another, such as JSON, XML, or CSV. The developer can specify the input and output paths for each field in the Transform tab. The developer can also use formulas to manipulate data in the Formula tab1. To transform contact data into a JSON array, the developer can use either of these methods:

Use a formula LIST(Contact), and add the output of the formula as the input in the Transform tab. This will create a list of contact objects from the input JSON and output it as a JSON array.

Set the Input JSON Path as Contact, the Output JSON Path as Contact, and the Output Data Type as List. This will output each contact object as an element of a JSON array.

When data changes every five minutes, the cache lifetime should be close to that refresh cycle. A 300-second Cache Duration gives the Integration Procedure a performance benefit while limiting stale data exposure to approximately the same interval as the source data change frequency. A contextual key controls cache separation by context, but it does not define when cached data expires. Disabling caching ignores the stated requirement that the developer wants to use caching. A very high value, such as 24 hours, is dangerous because users could receive stale data long after the underlying source changed. Salesforce’s OmniStudio caching guidance explains that Integration Procedures can cache results and that Cache Blocks are appropriate when different data must expire at different times.

================

From OmniStudio Best Practices for Modular Script Design, OmniScript Actions are the preferred mechanism to invoke another OmniScript within a parent OmniScript. This approach enables reusability and modularization, especially when a function (like updating billing information) is common across many interactions.

A. OmniScript Action – This is the correct and standard method for embedding or launching one OmniScript from another. It allows developers to reuse common scripts without duplicating logic.

Incorrect Options:

B. Custom Action requires custom Apex or LWC development, which is unnecessary for this use case.

C. Lightning Action is typically used to invoke OmniScripts from Lightning pages, not within OmniScripts themselves.

OmniStudio Developer Guide → OmniScript Actions

The merge code syntax for accessing a node from an Integration Procedure output is {{ProcedureName:NodeName}}. In this case, the ProcedureName is HTTPGetCaseDetails and the NodeName is CaseData. The % sign is used for single-value merge codes, not node merge codes. The $ sign is used for variables, not merge codes.

 According to the FlexCard Designer Overview page, another possible cause of a field showing only the label is that “the field is null on the Salesforce record”.

Integration Procedure is the correct tool because the requirement goes beyond a simple Salesforce record extraction. Complex filtering, sorting, aggregation, orchestration, and preparation should be handled server-side before the OmniScript displays the result. A Data Mapper Extract is appropriate for retrieving Salesforce data, but it is not the best orchestration layer when multiple operations and preparation logic are required. An HTTP Action only calls an external endpoint; it does not by itself manage the full data-preparation workflow. A Set Values Action is useful for assigning values in the OmniScript data JSON, not for complex server-side data shaping. Salesforce describes Integration Procedures as server-side processes used to automate data operations between Salesforce and external systems, which matches this requirement.

================

The Conditional View property on the Step elements is the correct client-side control. The branching depends on a value selected earlier in the OmniScript, and the constraint explicitly says not to use server-side logic. Conditional View can hide or show elements, blocks, or steps based on conditions in the OmniScript data JSON. Pub/Sub on FlexCard elements is unrelated because this is an OmniScript step-visibility problem, not inter-component messaging. An Integration Procedure conditional block would push the path decision to server-side logic, violating the requirement. A Data Mapper does not control UI step visibility. Salesforce documentation states that Conditional View hides an element or group of elements in a block or step based on specified conditions, which fits this scenario precisely.

================

The verified answer is C. The selected answer in the PDF appears to be wrong. For OmniStudio managed package runtime, upgrades are package-based and can require installing the newer managed package version. Salesforce documentation for installing or upgrading the OmniStudio package says to install the latest OmniStudio managed package by going to OmniStudio Managed Package Releases and using the installation URL. That is different from standard runtime behavior, where functionality is more directly tied to Salesforce platform releases. Option D incorrectly treats managed package runtime as automatically upgraded only through seasonal Salesforce releases. Option A is wrong because a support case is not the normal upgrade mechanism. Option B overstates the process; deactivating all components is not the defining characteristic.

================

 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.

In Preview, the JSON node that shows the data sent to the Response Action is the name of the Response Action itself. In this case, it is ResponseCart. The other nodes show either the input data or the output data of the Integration Procedure.

After defining a formula, the result must be stored and made available in the Data Mapper output structure. In the current Data Mapper design pattern, the formula result path creates a JSON node, and the developer then maps that result into the final output through the mapping configuration. This is why option B is the best answer: the formula is not useful to downstream actions until it is mapped to the required target output. The Extract tab is used to define source data retrieval, not to map formula results. The Output tab applies to specific Extract-style mappings in older terminology, but the question uses the generic Data Mapper mapping workflow. The essential step is to map the formula result into the JSON.

================

The cleanest method is to assign a unique CSS class to the second Block and apply the styling once at the Block level. This keeps the design maintainable because all less-critical fields inside that Block inherit or are affected by the same styling pattern. Manually changing each Text element works technically, but it is inefficient and harder to maintain if more fields are added later. A Layout property does not exist as a reliable “Small” styling switch for this requirement. A State element is for alternate card presentations based on conditions, not simply applying a different font style to one section. Salesforce FlexCard documentation supports applying custom CSS classes and inline styles to FlexCard elements when built-in style properties are not enough.

================

In OmniScripts, if you need to apply a function (like COUNTIF) to dynamic data and show the result immediately, the Formula element is the correct choice.

B. Formula element – The Formula element supports real-time calculation using OmniStudio expression functions (like COUNTIF, SUM, etc.) and updates values instantly on the screen without the need for server calls.

Incorrect Options:

A. Set Values element is used to set static or conditional values but doesn’t support formula evaluation.

C. Range element is used for value comparisons and conditions, not for calculations.

Salesforce OmniStudio Developer Guide → OmniScript Formula Element

According to the Transform External Data Unit, the Expected Output JSON should match the Output Path of the DataRaptor Transform. In option D, the Output Path is Current:CityState, which matches the Expected Output JSON. The other options have different Output Paths that do not match the Expected Output JSON. Therefore, the correct answer is D.

The correct declarative design is to use a Data Mapper Transform after the HTTP Action. The HTTP Action performs the REST call and returns the response to the Integration Procedure. If that response must be converted from JSON into a required XML structure, the transformation layer should be a Data Mapper Transform, because transforms are built to map input paths to different output structures and formats without writing Apex. XMLStreamReader is for reading XML, not building the target XML payload from JSON. XMLStreamWriter could be used in custom Apex, but the OmniStudio-native answer avoids unnecessary code. A Data Mapper Extract reads Salesforce data, so it is not the right tool for restructuring an HTTP response.

================

A DocuSign Envelope Action can be used to create and send a document for signature using a DocuSign template. The developer can specify the template ID, recipient details, and prefill data in the action configuration

In Expression Sets, for any intermediate step (like Calculation) to be referenced in subsequent steps, such as Aggregation, the value must be made available via Output.

B. It must be included in the output – Correct. Each step has an " Include in Output " checkbox. If not checked, its result is not accessible to following steps like Aggregation or Sub Expression.

Incorrect Options:

A. Constants are global but do not affect step dependency.

C. It does not have to be a Calculation Step; any previous step’s output can be used if exposed.

Salesforce OmniStudio → Expression Sets - Step Configuration

The wording of this question is imperfect. Official Salesforce documentation identifies the OmniStudio Build Tool, formerly Vlocity Build Tool, as the Node.js command-line automation tool designed to package, export, and deploy OmniStudio DataPacks in a source-control-friendly format. Since “OmniStudio Build Tool” is not one of the listed choices, the only command-line deployment option given is Salesforce Command-Line Interface. Visual Studio Code Integrated Terminal is merely a shell host, not a migration tool. Metadata API is a deployment API, not the OmniStudio-specific CLI named in the documentation. Change Data Capture is an event-streaming feature and has nothing to do with OmniStudio component migration. So D is the only usable answer from the provided options, but the technically precise tool name is OmniStudio Build Tool/Vlocity Build Tool.

================

 According to the OmniStudio Developer Guide, “To upsert a record, select the Upsert Key checkbox for the field that contains the unique identifier for the record. If you want to create a new record when no match is found, select Is Required for Upsert.” Therefore, the correct answer is B.

The Target property in publishing Options determines where the FlexCard will be displayed. Setting it to the Community page will make the FlexCard available in the community

The Remote Action node is identified by the element name configured in the Integration Procedure. Since the Remote Action is named FetchCart, the relevant Preview JSON node for that action is FetchCart. The debug-specific node, such as FetchCartDebug, is used for diagnostic details, not as the primary action node being evaluated in this question. ResponseCart and ResponseCartDebug belong to the Response Action, not the Remote Action. Salesforce documentation confirms that a Remote Action in an Integration Procedure calls the specified Apex class, method, or invocable action, and Integration Procedure actions are configured and executed as named elements in the procedure sequence.

================

The correct tool is the Test Data and Parameters panel in the FlexCard Designer. The requirement is specifically to test the FlexCard directly in its designer with different JSON inputs before deployment. The OmniScript Test Console is for OmniScript logic, not FlexCard data rendering. IDX Workbench is a migration/deployment tool, not the FlexCard’s built-in data-testing panel. A Data Mapper Turbo Extract preview only tests the Data Mapper query output; it does not validate how the FlexCard processes different JSON structures and renders states, fields, or conditional elements. Salesforce documentation for FlexCard testing describes adding test parameters in the FlexCard Designer and previewing/debugging the card using those values, which directly supports option C.

================

The first responsible action is to validate the Data Mapper query design before committing to the implementation. Prefilling 15 user-based fields can be efficient, but only if the query is selective, returns only needed fields, and uses appropriate filters. Salesforce’s Data Mapper best practices warn developers to avoid server performance problems and to ensure filtering and sorting operations use indexed fields where possible. A Data Mapper Load is wrong because the requirement is to read current user data, not write data back to the User object. Converting the process to a FlexCard does not solve the prefill query risk. A Formula element cannot query Salesforce records. Therefore, option A is the correct risk-reduction step before development proceeds.

For an active OmniScript, the correct practice is to create a new version, make the change in that new version, test it, and activate it only when it is ready. Editing the active version directly is risky because users can be affected immediately, and in-flight users may experience inconsistent behavior. Cloning creates a separate component and is useful when the new script must be independent, but it is not the best approach for a minor controlled change to the same OmniScript. Waiting for a Salesforce release is irrelevant because this is a configuration lifecycle issue, not a platform-release dependency. Salesforce’s OmniStudio versioning guidance supports using versions so changes can be validated before replacing the active version used by end users.

================

The correct approach is to use the responsive sizing properties available in the element Display configuration, such as Extra Small, Small, Medium, and Large. These settings align the element with the responsive grid model instead of forcing custom widths. Newport Design System styling is intended to provide consistent visual behavior across OmniScripts and FlexCards, so using framework-supported sizing is cleaner than hard-coding CSS. Option B can add utility classes, but it is not the primary standard grid-sizing property for the input element. Option D is weaker because custom CSS makes the layout harder to maintain. Option A is unrelated because Repeat CSS is not the standard way to control horizontal grid width.

================

Invoke Mode Non-Blocking is the correct choice because the OmniScript still needs the Integration Procedure response, but the user interface should not be blocked while waiting. Salesforce describes Non-Blocking as running asynchronously while applying the response to the UI. Fire and Forget is different: it is used when the caller does not need a response returned to the OmniScript. Use Future is also asynchronous, but it is best when completion timing is not critical and no response is required. Toast Completion only controls a user notification style; it does not determine whether the OmniScript waits for the Integration Procedure response. Since the response must still come back as JSON while the user proceeds, Non-Blocking is the correct feature.

================

 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.

The Lookup element is used to retrieve data from a single field in a Salesforce record. The Lookup element allows the developer to specify the object, field, and filter criteria for the data retrieval. The Select element is used to display a list of options for the user to choose from. The HTTP Action element is used to send or receive data from an external system using HTTP methods. The DataRaptor Post Action element is used to create or update Salesforce records using a DataRaptor Transform.

he Aggregation Step in a calculation procedure allows the developer to perform aggregate functions such as SUM, COUNT, MIN, MAX, and AVG on the output of a previous step. The developer can use this step to calculate the sum of the entire base price by specifying the field name and the aggregation function

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

For off-platform use, OmniStudio uses OmniOut so LWC OmniScripts and FlexCards can run on third-party websites. Salesforce documentation explains that an activated OmniScript can be downloaded as an Off-Platform LWC and then added to the OmniOut project for integration into the external application. This makes option B correct because the external site embeds the OmniScript as a Lightning Web Component artifact, not as a Visualforce page. Visualforce is Salesforce-hosted legacy UI technology and is not the primary external embedding model. A REST API could call backend logic, but it would not render the OmniScript user interface. An Integration Procedure call only executes server-side logic; it does not embed the guided OmniScript experience.

================

The correct parameter is ContextId. When an OmniScript is launched from a Lightning Record page, Salesforce passes the current record ID into the OmniScript as a context ID. The OmniScript can then use ContextId to query related data through Data Mapper Extracts, Integration Procedures, or other actions. Using AccountId might work only if the developer manually maps that value, but it is not the standard automatic page-context parameter. recordId is common in Lightning Web Components, but OmniScript’s record-page launch behavior uses ContextId. CurrentRecord is not the standard OmniStudio parameter. Salesforce documentation explicitly states that, by default, the record ID on a Lightning Record page passes into the OmniScript as a context ID.

================

FlexCards support embedding a custom Lightning web component through the Custom LWC element. The developer should drag the Custom LWC element onto the FlexCard canvas and configure the component name so OmniStudio knows which Lightning web component to render. Using an HTML element with an lwc tag is not the supported declarative method and can create security, rendering, and maintenance problems. An Action element is used to trigger behavior such as launching flows, OmniScripts, or navigation, not to host an LWC visually inside the card. Option D is also wrong because the configuration does not point to a “Card” property for the Lightning web component. The required implementation is the Custom LWC element with the component name configured.

================

According to the OmniStudio Developer Guide, “To return a response from an Integration Procedure, add a Response action as the last action in your Integration Procedure.” Therefore, the correct answer is C.

According to the OmniScript Data JSON page, the OmniScript structure JSON defines the data elements and their properties that are used in an OmniScript. The exhibit shows an OmniScript structure JSON with six elements: AccountName, AccountNumber, AccountType, AccountOwner, ContactName, and ContactPhone. The DRGetAccountDetails action is a DataRaptor Extract action that retrieves data from the Account and Contact objects in Salesforce. The BlkContacts element is a Repeat Block that displays a list of contacts related to the account. Therefore, the JSON from the DRGetAccountDetails action that would display all six values correctly in the OmniScript structure shown is option C, which has the following structure:

{ The other options have different structures that do not match the OmniScript structure shown. Therefore, the correct answer is C.