Understanding DataMapper Turbo Extract in OmniStudio

In Salesforce OmniStudio, DataRaptors are essential tools for handling data efficiently. Among them, DataRaptor Turbo Extract is designed for high-speed data retrieval with minimal processing. Unlike the standard DataRaptor Extract, Turbo Extract is optimized for performance and simplicity, making it an excellent choice for retrieving data from a single object.

In this blog, we will explore the fundamentals of DataRaptor Turbo Extract, how to configure it, and best practices for using it effectively.

---

What is DataRaptor Turbo Extract?

DataRaptor Turbo Extract is a streamlined version of DataRaptor Extract, focusing on retrieving data faster with fewer processing steps. It is limited to extracting data from a single object, though it allows selecting fields from related objects.

Key Features:

• Retrieves data from one Salesforce object

• Supports related objects for field selection

• Allows filtering to fetch only required records

• Does not support transformations or custom JSON structures

• Optimized for performance and quick execution

Why Use DataRaptor Turbo Extract?

• Speed & Performance – Reduces processing time by eliminating transformations.

• Simplicity – Easy to configure with fewer settings.

• Optimized Queries – Retrieves only the necessary fields, improving efficiency.

Scenario: When to Use Turbo Extract

Imagine a customer service center where agents need to quickly access case details and related contact information in an OmniScript. For this, we need:

• DataRaptor Turbo Extract – To fetch Case details and associated Contact details.

• DataRaptor Load – To update the case information.

• Integration Procedure – To connect and process the data.

• OmniScript – To display the retrieved details.

Turbo Extract helps speed up the data retrieval, ensuring agents get the necessary information quickly.

Steps to Create a DataRaptor Turbo Extract

Step 1: Define Basic Information

When creating a DataRaptor Turbo Extract, you need to specify the following:

• Interface Type: Select Turbo Extract.

• Input Type: JSON (for OmniScript) / XML / Custom.

• Output Type: JSON (for OmniScript) / Custom.

• Permissions (Optional): Define required access controls.

• Description (Optional): Add a brief note about its purpose.

Step 2: Configure Extract Settings

To extract data, configure the Extract Tab with these details:

• SObject Selection – Choose the Salesforce object (e.g., Case).

• Extract Output Path – Define the top-level JSON node in the output.

• Filter Criteria – Apply conditions to fetch only the required records.

• Matches Conditions – Use operators like =, <, >, LIKE, IN, etc.

• Additional Filters – Use AND, OR, LIMIT, ORDER BY, OFFSET for refined queries.

• At least one filter condition is mandatory for extracting data.

Step 3: Select Fields for Extraction

• Choose fields from the main SObject.

• Use related objects to select additional fields.

• Keep the field selection minimal to improve performance.

Step 4: Preview & Validate the Output

• After adding filter conditions and selecting fields, use the Preview Tab to check the expected JSON output.

• Ensure that data is being fetched correctly before integrating it into an OmniScript.

Integrating Turbo Extract with OmniScript

To display the retrieved data in an OmniScript, follow these steps:

1. Pass Context ID from OmniScript to Integration Procedure.

2. Call Turbo Extract within the Integration Procedure as a Data Source.

3. Map JSON Nodes correctly to the OmniScript fields (Ensure element names match JSON node names).

4. Place the Integration Procedure before the Step element in OmniScript.

5. Test the Setup by passing a valid Case ID in the Preview tab.

Important Note: If the JSON node names from Turbo Extract do not match the OmniScript elements, data will not be displayed correctly.

Conclusion

DataRaptor Turbo Extract is a powerful and efficient tool for retrieving Salesforce data quickly. By using it effectively, you can significantly improve the performance of OmniScripts and Integration Procedures. If transformations or multi-object data retrieval are needed, consider using DataRaptor Extract instead.

In our next blog, we will cover DataRaptor Load and how to map fields for updating Salesforce records. Stay tuned.