Data Modeling and Management20% of the exam
Relationship types: sharing, deletion and report types
What lookup, master-detail, many-to-many, external lookup and indirect lookup relationships do to record access, deletion and undelete, page layouts and standard report types, and what changes when you convert a lookup to master-detail or back.
Given a scenario, explain the capabilities of the various relationship types and the implications of each on record access, user interface, and reporting.
~8 min read · 16 practice questions ·
What the exam expects
- Compare lookup and master-detail on ownership, access, deletion and layouts.
- Predict access to detail and junction records.
- Predict delete and undelete results.
- Explain what converting a relationship does to sharing, data and reports.
- Pick the standard report type a relationship provides, and explain external and indirect lookups.
Key terms:
- Controlled by Parent: the sharing default of a detail object; access comes from the master record.
- Sharing Setting: the master access (Read Only or Read/Write) needed to create, edit or delete details.
- Primary master: the first master-detail relationship created on a junction object.
- External lookup: links a child to a parent external object by its External ID standard field.
- Indirect lookup: links a child external object to a standard or custom parent by a custom unique External ID field.
Key facts
Relationship limits
- Detail
- 2 master-detail; 40 total by default, up to 50 on request
Detail ownership
- Detail
- No Owner field; no sharing rules, manual sharing or queues
Master-detail field on layout
- Detail
- Always required on the detail page layout
Separately deleted detail
- Detail
- Can't be undeleted after its master is deleted
Delete this record also
- Detail
- Disabled by default; bypasses security and sharing
Junction, both masters deleted
- Detail
- Junction record deleted permanently
Junction delete limit
- Detail
- Over 200 junction records plus a roll-up to the other parent blocks deleting a parent
Master-detail to lookup
- Detail
- Needs no roll-ups on the master; detail default becomes Public Read/Write
Lookup to master-detail
- Detail
- Every record needs a value; default becomes Controlled by Parent
- Why can't a detail object use sharing rules or queues?
- When does deleting a parent of a junction object fail?
- Why might an object not appear as a parent for an indirect lookup?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform App Builder pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 26 lessons of the Platform App Builder guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (16 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams