Data Mappers17% of the exam
Choosing Extract, Turbo Extract, Load or Transform
Which of the four Data Mapper types fits a requirement: Turbo Extract for fast single-object reads with parent fields, Extract for child lists, formulas, defaults and XML, Load for writes with formulas, and Transform for reshaping data in memory with no SOQL.
Differentiate and recommend the correct Data Mapper type (Extract, Turbo Extract, Load, Transform) based on the specific business need.
~8 min read · 10 practice questions ·
What the exam expects
- Recommend a Turbo Extract, Extract, Load or Transform from what the step must do: read, write or reshape, and with which extras.
- Explain why a Turbo Extract is the fast choice for one object plus parent fields, and name the needs that rule it out (child lists, formulas, default values, XML output, several apostrophe inputs).
- Recognise that Extract, Load and Transform all support formulas, so a calculation alone never forces an extra Data Mapper.
- Recommend a Transform when data is already in memory and no SOQL query may run.
- Confirm that Data Mappers read custom metadata types declaratively, with no Apex.
Key terms: Interface Type (the Data Mapper type, chosen at creation); related objects (parent fields a Turbo Extract selects); extract step (one object queried by an Extract); Formula Result Path (the node that holds a formula result); Output Type (the format a Data Mapper returns).
Key facts
Turbo Extract reads
- Detail
- One object type plus fields from related (parent) objects
Turbo Extract can't use
- Detail
- Formulas, custom JSON, default values, transformations
Turbo Extract relationship depth
- Detail
- Up to five relationship levels, child-to-parent only
Turbo Extract LIMIT
- Detail
- 1 through 50000; default 50000
Apostrophes in several inputs
- Detail
- Not supported on a Turbo Extract; use an Extract
Child record lists
- Detail
- Need an Extract with at least two extract steps
Formula support
- Detail
- Extract, Transform and Load; Turbo Extract doesn't
Output Types
- Detail
- Extract JSON/XML/Custom; Turbo JSON/Custom; Load sObject; Transform adds PDF, Docusign, Document Template
Transform and SOQL
- Detail
- Works in memory; no SOQL or other Salesforce reads
Custom metadata
- Detail
- Readable by Data Mappers with no special syntax
Load in Preview
- Detail
- Changes are saved permanently to Salesforce
Sources for this section (6)
- Omnistudio Data Mappershelp.salesforce.com (opens in a new tab)
- Configure a Data Mapper Turbo Extracthelp.salesforce.com (opens in a new tab)
- When to Use Multiple Extract Stepshelp.salesforce.com (opens in a new tab)
- Use Formulas in Omnistudio Data Mappershelp.salesforce.com (opens in a new tab)
- Designing Data Mappers for Optimal Performancetrailhead.salesforce.com (opens in a new tab)
- Understanding Data Mapper Typestrailhead.salesforce.com (opens in a new tab)
- Why can't a Turbo Extract on Account return every related Contact on Standard Runtime?
- When should a consultant recommend a Transform rather than an Extract on Standard Runtime?
- Which Output Types can a Turbo Extract return?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 31 lessons of the Omnistudio Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (10 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams