Summary
When troubleshooting a DataRaptor Extract, the most efficient first step is to use the integrated Preview tab within the DataRaptor interface itself. This tool allows you to execute the DataRaptor in isolation by providing a sample JSON input. It immediately shows the output or any errors, confirming whether the issue lies within the DataRaptor's configuration (like the JSON extract map) or elsewhere in the integration.

Correct Option

B. Go to the PREVIEW tab In OmniScript to test.
This is the correct first step because the Preview tab is a dedicated, controlled environment for testing DataRaptors. You can provide a specific input JSON that mimics what your OmniScript would send, and the tab will display the exact output the DataRaptor returns.

This isolates the DataRaptor's functionality. If it fails here, the problem is definitively within the DataRaptor's configuration (e.g., an incorrect field mapping or object relationship). If it works here, the issue likely lies in how it's being called from the OmniScript or Integration Procedure.

Incorrect Option

A. Go to the Lightning Console and reload the page to test.
This is an inefficient first step. Reloading an entire application page involves many other components (the OmniScript, layouts, other data sources). It does not isolate the DataRaptor, making it difficult to pinpoint the root cause of the data retrieval issue.

C. Deactivate the card and layout, and go to the PREVIEW tab for the card to test.
This approach is overly complex and indirect for the stated goal. The Card's Preview tab tests the entire card, not just the DataRaptor. Deactivating components is unnecessary when a direct testing tool for the specific component in question is available.

D. Add a key/value pair in the DataRaptor to test it.
Modifying the DataRaptor by adding new elements should not be the first troubleshooting step. The correct initial action is to diagnose the current configuration using the Preview tool. Making changes before understanding the problem can introduce new errors and is not a systematic debugging approach.

Reference
Salesforce OmniStudio Developer Guide: Test a DataRaptor

Explanations

A. The missing data is trimmed in the Integration Procedure Action Response JSON Path.
The Response Action in the Integration Procedure (IP) or the Response JSON Path setting on the Integration Procedure Action within the OmniScript controls what data gets returned from the IP to the OmniScript's Data JSON.

If the Response JSON Path is configured to point to a specific sub-node of the IP's output (e.g., Result:AccountData), only the data under that node is returned.

If the missing data lives outside that specified path, it is trimmed or excluded from the response, and the OmniScript never receives it.

B. The element name for the missing data does not match the JSON node key in the Integration Procedure Response.
Data mapping in an OmniScript is case-sensitive and relies on a direct name match between the OmniScript element's Element Name and the JSON node key from the Integration Procedure's response.

If the Integration Procedure returns a key named "annualRevenue", but the OmniScript element is named "AnnualRevenue", the OmniScript will not automatically populate the field, and the data will appear missing to the user.

❌ Why the other options are incorrect:

C. The Integration Procedure Preview Input Parameters do not match the JSON sent from the OmniScript: This only affects how the developer tests and debugs the IP in its own preview pane. It does not affect the runtime behavior of the Integration Procedure when it is called from the OmniScript, as the OmniScript provides the live input JSON.

D. The JSON sent from the Integration Procedure Action does not match any of the Original Input for the Integration Procedure: This statement is confusing and generally incorrect. The Integration Procedure Action receives data from the IP. The IP's Original Input configuration is a design-time best practice that doesn't strictly prevent data from being processed; data is read dynamically from the Data JSON. A mismatch here would more likely cause an error or data loss within the IP (e.g., if a subsequent action fails to find the expected input) rather than a partial display failure in the OmniScript.

Summary
Performing complex, multi-step calculations on each item in an array requires a specialized and scalable approach. The logic needs to be applied iteratively, and using tools designed for bulk or iterative processing is a best practice. This ensures maintainability, performance, and separation of concerns, rather than building complex, nested logic directly within the Integration Procedure.

Correct Option

B. Use a Calculation Action to call a Calculation Procedure.
A Calculation Procedure is the primary tool for complex, multi-step calculations in OmniStudio. It can be designed to accept a single record (one element of the array) as input, perform the necessary calculation steps, and return a result. By placing this action inside a Loop Block that iterates over the array, you can efficiently process each element with the robust calculation logic.

D. Use a Matrix Action to call a Calculation Matrix.
A Calculation Matrix is ideal for calculations that are based on predefined rules and input/output mappings (e.g., tax tables, pricing rules). If the multi-step calculation can be defined as a set of rules in a matrix, this is a highly efficient and maintainable method. The Matrix Action can be used inside a Loop Block to apply these rules to each element in the array.

Incorrect Option

A. Use a ListAction to merge the array elements together.
A ListAction is used to perform simple operations on a list as a whole, such as merging two lists or converting a list to a string. It is not designed for performing iterative, multi-step calculations on individual elements within an array.

C. Use a Set Values Element inside a Loop Block.
While a Loop Block is correct for iteration, a Set Values element is too simplistic for a "multi-step calculation." Set Values is for assigning values, not for complex mathematical or logical operations. For anything beyond the most basic assignment, using a dedicated calculation tool (Calculation Procedure or Matrix) is the recommended best practice.

Reference
Salesforce OmniStudio Developer Guide: Calculation Procedure Action
Salesforce OmniStudio Developer Guide: Calculation Matrix Action

Summary
Within an Integration Procedure, data is passed between elements using a specific merge field syntax. This syntax allows you to reference the output of a previous action to dynamically build values, such as a URL in an HTTP Action. The correct syntax uses a specific set of delimiters and follows a structured path to identify the source element and the desired data node.

Correct Option

D. {(SetValues.Date)}
This is the correct merge field syntax for referencing data from a previous element within an Integration Procedure. The double curly braces {{...}} are the standard delimiters. SetValues is the name of the previous element, and Date is the specific node within that element's output that you want to insert into the URL.

Incorrect Option

A. x%SetValues.Date%
This syntax is incorrect. It uses percent signs % as delimiters, which is the syntax used for merge fields within an OmniScript's text elements, not for referencing data between actions within an Integration Procedure.

B. (‘ Setvalues’] [ ‘Date’]
This syntax is completely invalid and does not conform to any merge field pattern in OmniStudio. It uses square brackets and quotes incorrectly.

C. %SetValues Date
This is also incorrect. It uses the wrong delimiter (a single percent sign) and is missing the period . that separates the element name from the node name. The correct format requires double curly braces and proper dot notation.

Reference
Salesforce OmniStudio Developer Guide: Integration Procedure Data Pipelining