Data Mapper Series: Deep Dive into Turbo Extract

Hello everyone, and welcome back! Today, we are kicking off our detailed series where we will explore every single type of Data Mapper in OmniStudio.

Before we jump into today’s session, if you are new to this topic, I highly recommend checking out my previous blog post to get a high-level overview of what a Data Mapper is and how it fits into the overall architecture.

Alright, let’s get started!

As you can see in the image below, Data Mappers are divided into four main categories based on the specific job they need to do with your Salesforce data:

• Turbo Extract: Used to retrieve data from a single Salesforce object as quickly as possible.
• Extract: Used to retrieve complex data from multiple related Salesforce objects at the same time.
• Load: Used to save, create, or update records back into your Salesforce database.
• Transform: Used to restructure, rename, or change the format of your data without interacting with the database.

DataMapper Types

Every Data Mapper has its own specific superpower, and we choose which one to use based on our exact data requirements. Today, we are putting the spotlight on our first contender: Turbo Extract.

Let’s Build Your First Turbo Extract!

Ready to get your hands dirty? Follow these simple steps to create your very first Turbo Extract Data Mapper:

• Launch the App: Click on the App Launcher (the nine dots in the top left) and search for the OmniStudio app.
• Find the Component: Once the app opens, click on the navigation menu and select Data Mappers.
• Create New: Click the New button to start building.
• Configure the Details: A setup box will appear. You need to configure it like this:
• Name: Give your Data Mapper a clear, unique name.
• Interface Type: Select Turbo Extract from the dropdown.
• Input & Output Type: Select JSON for both.
• Save: Click the Save button, and boom — your new Data Mapper is created and ready for action!

🎉 Woohoo! Your Turbo Extract is Ready!

Turbo extract is basically used for fetching data from single object.

Let’s quickly review the golden rule of the Turbo Extract: It is designed to fetch data from a single Salesforce object. Because its job is so focused and lightning-fast, the builder interface is super simple. In fact, it only has one main configuration tab where you set everything up!

Let’s Look at a Real Example

Imagine we want to fetch basic details — like the ID, Name, and Phone Number — for a specific Account in Salesforce. Here is exactly how we set that up:

1. Go to the Extract Tab: This is the main screen where all the magic happens.

2. Select the Object: From the dropdown menu, select Account (since that is the object holding our data).

3. Set the Extract Output Path: Think of this as the name of the “bucket” that will hold your data once it is fetched. You can name it anything you want, but for this example, let’s name it AccountData

4. Set the Filter (The “Where” Clause): We don’t want to fetch every Account in Salesforce; we only want one specific Account. We use the filter to tell the system exactly what to look for :

• Filter Field: Select Id
• Operator: Select =
• Value: Type in AccountId (this acts as a variable that we will pass in later to find the exact record).

🎯 Picking Your Fields (No Code Required!)

If you think about it, what we just did in the Extract step is exactly like writing a database query (like a SOQL query) — but in a simple, point-and-click format. No coding required!

Now that we’ve told the Data Mapper which record to find, we need to tell it what information to bring back.

• Select Your Fields: Look for the Search Fields section on your screen.
• Search for and select the specific fields we need for our example: Id, Name, Type, and Website

The Moment of Truth: Let’s Preview It!

We’ve built it, but does it work? The Preview tab is your best friend — it lets you test your Data Mapper in real-time to make sure it’s pulling the right data before you ever use it in a live application.

Here is how to run your test:

1. Click over to the Preview tab at the top.
2. Look for the Input Parameters panel.
3. Key: Type in AccountId (this must exactly match the variable name we created in our filter earlier).
4. Value: Go into your Salesforce org, copy a real Account ID from the URL of any Account record, and paste it here.
5. Execute: Hit that Execute button and watch the magic happen!

If everything is set up correctly, you will see a beautiful JSON response pop up on the right side of the screen containing the exact Id, Name, Type, and Website of the Account you searched for.

Preview Tab

📊 Reading Your Results (Did It Work?)

Once you hit that Execute button, here is exactly where you need to look to see what happened:

The Canvas (The Good Stuff!): If everything worked perfectly, your shiny new data will be displayed right here in the main canvas area. It will be neatly formatted in JSON, looking exactly like the example below!

The Errors Section (Uh-Oh!): We all make mistakes! If something went wrong — maybe you missed a letter when copying the Account ID — don’t panic. Just look on the right-hand side of your screen under the Errors section. The system will tell you exactly what tripped it up so you can fix it.

Debug Logs (For the Curious Minds): Want to see what the engine is doing under the hood? Check the Debug Logs. Even though you used a point-and-click tool to build this, Salesforce translates it into a real database query behind the scenes. You can peek in the logs to see the actual SOQL query it generated!

Debug Logs

🚀 What’s Next?

That’s a wrap on our Turbo Extract journey! You now know how to pull data from Salesforce at lightning speed.

But what if you need to pull data from multiple related objects at the same time? In our next blog of the Data Mapper series, we are going to level up and tackle the Extract Data Mapper (the ultimate multi-tasker).

Stay tuned, and happy building! ✨