If you've spent any time in OmniStudio, you've probably wondered when to reach for a DataRaptor Turbo Extract instead of the standard Extract. It's one of those choices that seems small at first, but it can actually make or break the performance of your FlexCards or OmniScripts. I've seen plenty of teams struggle with slow page loads simply because they used the wrong tool for a basic data pull.
Why DataRaptor Turbo Extract is usually the better choice
DataRaptor Turbo Extract is built to be fast. It skips the heavy lifting the classic Extract does, like complex mapping and formulas. It goes straight to the Salesforce database, grabs the fields you asked for, and hands them back in a flat JSON structure.
In my experience, if you're just trying to populate a simple list of records, Turbo is the way to go. It uses fewer server resources and has lower latency. When you're managing large data volumes, those milliseconds add up quickly. If you can use Turbo, you should.
Comparing DataRaptor Turbo Extract and the classic Extract
So what's the catch? The Turbo speed costs you flexibility. Think of it this way: Turbo is a motorcycle, fast but unable to carry much. The classic Extract is a moving truck. It takes longer to get there, but it can carry your whole house and rearrange the furniture on the way.
- Mapping: Turbo gives you the data exactly as it looks in Salesforce. Classic lets you rename fields, nest them, and create a custom JSON structure.
- Formulas: if you need math or string manipulation inside the DataRaptor, you need the classic version. Turbo doesn't support complex formulas.
- Relationships: Turbo handles a single object and its immediate parents. If you need to pull from multiple unrelated objects or do complex joins, you'll hit a wall.
- Performance: Turbo wins every time. It's optimized for high-traffic screens where you just need raw data quickly.
I always start with a Turbo Extract. If I find later that I need to transform the data or add a formula, I can switch to a classic Extract. Going the other direction is much harder once you've built out a complex mapping.
When to stick with the classic Extract
The classic DataRaptor Extract isn't obsolete. You need it whenever you have to shape the output for a specific integration or a complex UI component. If your JSON has to be deeply nested, or you're using Data Masks to hide sensitive info, Turbo won't get you there. And if you're following strict OmniScript naming conventions and need your output paths to match a specific schema, the mapping tab in the classic version is where you live.
Limitations of the Turbo method
One thing that trips people up is the relationship limit. DataRaptor Turbo Extract can pull from related objects (getting the Account Name from a Contact record, for instance), but it isn't designed for deep traversals. If you find yourself reaching four or five levels away, you're going to run into trouble. At that point you're better off with a classic Extract, or an Integration Procedure to stitch the data together.
Key takeaways
- Use DataRaptor Turbo Extract for 90% of your simple read operations to keep performance high.
- Choose the classic Extract only when you need formulas, complex JSON nesting, or data masking.
- Turbo returns a flatter JSON structure, which is usually easier for FlexCards to handle anyway.
- Always benchmark your load times. If a page feels sluggish, check your DataRaptors first.
Don't over-engineer your data layer if you don't have to. If you're just getting started with these tools, build the same simple query in both versions and compare the response times in the OmniStudio debugger. The gap shows up straight away.
Leave a Comment