Data Mapper Load: link mappings and interface objects
How a Data Mapper Load writes to several objects: object order and Add Link, field mapping settings (Default Value, Upsert Key, Lookup), XML input, the Options tab, the three input sources, and interface objects with their reserved DM fields and Delete On Success.
Configure and import data to multiple objects using load interface.
~8 min read · 7 practice questions ·
What the exam expects
- Add several objects to a Load in the right order and relate records created in the same run with Add Link.
- Configure field mappings: Input JSON Path, Domain Object Field, Output Data Type, Default Value, Upsert Key, Required for Upsert and Lookup.
- Feed a Load from an Omniscript or Integration Procedure, a REST POST or Apex, including XML input from a callout.
- Set Load options such as Delete On Success and Is Default For Interface, and know which ones other units teach.
- Build an interface object for bulk external data: reserved DM fields, the trigger and future class, and SObject input.
Key terms: Load object (an object on the Objects tab the Load writes to, numbered in sequence), link mapping (Add Link: fills a field with a value from another object in the same Load), Upsert Key (a mapping flag that decides update versus insert), interface object (a custom object that holds imported rows for a Load), DMProgressData (the reserved field that receives created record Ids).
Key facts
- Detail
- On the source object (the one with the lookup field)
- Detail
- Domain Object Field, Linked Object, Linked Field
- Detail
- Default Value
""for null string fields
- Detail
- A null value prevents the record update
- Detail
- Omniscript or IP JSON, REST POST payload, Apex parameter
- Detail
- Load and Transform accept XML payloads
- Detail
- sObject input: deletes bulk records after a successful load
- Detail
- DMError, DMProgressData, DMName (required), DMStatus
- Detail
- Written to DMProgressData
- Detail
- Records in Objects Created are saved permanently
Sources for this section (6)
- Link Mappingshelp.salesforce.com (opens in a new tab)
- Configure Loadhelp.salesforce.com (opens in a new tab)
- Data Mappershelp.salesforce.com (opens in a new tab)
- Inputs and Outputshelp.salesforce.com (opens in a new tab)
- Interface Objectshelp.salesforce.com (opens in a new tab)
- Preview and Testhelp.salesforce.com (opens in a new tab)
- Why can't a Lookup fill the new Contact's AccountId when the same Load creates the Account?
- When do Delete On Success and Is Default For Interface apply?
- Why does Help's interface-object trigger skip an updated row whose DMStatus, DMError, DMProgressData or DMName changed?
- Why should you test a Load in Preview with throwaway data?
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