Data Mapper Extract steps, filters and relationships
How to chain extract steps with filters that point at earlier steps, predict the nested output JSON, read parent fields with relationship notation, and use filter operators, LIMIT, OFFSET, ORDER BY and environment variables in a Data Mapper Extract.
Configure and retrieve data from multiple objects with various filter options using Extract Interface.
~8 min read · 7 practice questions ·
What the exam expects
- Decide how many extract steps a requirement needs from how the objects are related (single object, parent fields, child records).
- Write step filters that reference an earlier step with the full object path, and predict the nested JSON the Extract returns.
- Read parent fields with relationship notation in Extract JSON Paths instead of an extra step.
- Configure filter operators (Equals, INCLUDES, AND/OR), LIMIT, OFFSET and ORDER BY, and use environment variables as filter values.
- Inspect what each step returns with View Extraction Step JSON before mapping.
Key terms: extract step (one object read on the Extract tab, with its Extract Object Path and filter), Extract Object Path (where the step's records sit in the extraction step JSON, such as Account:Case), relationship notation (a dot path to a parent's field, such as Account.Name), Extract JSON Path (the source path a mapping reads), OFFSET (where record retrieval starts, read from an input node).
Key facts
- Detail
- Objects are queried in the order of the extract steps
- Detail
- Need at least two extract steps
- Detail
- Uses the complete hierarchy, such as
Id = Account:Case:ContactId
- Detail
- Relationship name (
Account.Name), child to parent only
- Detail
- 1 through 50000; default 50000
- Detail
- Dynamic input node; integer 0 to 2000
- Detail
- Multi-select picklist fields only
- Detail
- SOQL sorts nulls first by default
- Detail
- Double-quoted and case-sensitive
- Detail
- 100 queries per Apex transaction; exceeding it fails the Data Mapper
Sources for this section (6)
- Multiple Extract Stepshelp.salesforce.com (opens in a new tab)
- Three Related Objectshelp.salesforce.com (opens in a new tab)
- Relationship Notationhelp.salesforce.com (opens in a new tab)
- Configure Extracthelp.salesforce.com (opens in a new tab)
- ORDER BYdeveloper.salesforce.com (opens in a new tab)
- Environment Variableshelp.salesforce.com (opens in a new tab)
- Why does the Case step in Help's example filter on
AccountId = Account:Idand notAccountId = Id? - When is relationship notation not an option?
- Why can't an OFFSET filter hold the literal value 20?
- What does a child step with three matching records return under its parent node?
- Where do you see every field an extract step can return?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 46 lessons of the Omnistudio Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (7 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams