Data Modeling and Management20% of the exam
Data model design: objects, junctions and Schema Builder
How to turn a requirement into objects, fields, record types and relationships: when a related custom object beats more fields, how to build a junction object, which structures force a lookup instead of master-detail, what Schema Builder can and can't do, and how to read Salesforce Architects data model diagrams.
Given a scenario, determine the appropriate data model.
~7 min read · 14 practice questions ·
What the exam expects
- Decide whether a requirement needs a field, a record type, a related custom object or a junction object.
- Build a junction object the recommended way.
- Recognise structures that must be a lookup instead of master-detail.
- Know what Schema Builder can add and its considerations.
- Read a Salesforce Architects entity relationship diagram (ERD).
Key terms:
- Data model: the objects and fields in an app; objects are tables, fields columns, records rows.
- Junction object: a custom object with two master-detail relationships linking two objects many-to-many.
- Self-relationship: a relationship from an object to itself; always a lookup.
- Hierarchical relationship: a special lookup available only on the User object.
- Record type: a variant of one object with its own business process, picklist values and page layout.
Key facts
Junction object
- Detail
- A custom object with two master-detail relationships
Self-relationships
- Detail
- Must be a lookup; a record can't link to itself
Many-to-many self-relationship
- Detail
- Not supported: a junction's two masters can't be the same object
Detail levels
- Detail
- Up to 3 custom detail levels
Standard objects in master-detail
- Detail
- Can be the master; can't be the detail of a custom object
Relationship limits
- Detail
- Up to two master-detail and 40 total relationships per custom object
Schema Builder adds
- Detail
- Custom objects, lookups, master-detail, all custom fields except Geolocation
Schema Builder field access
- Detail
- New custom fields visible and editable for internal profiles by default
Schema Builder limits
- Detail
- No schema export; Auto-Layout can't be undone; zoom not saved
Sources for this section (5)
- Many-to-Many Relationshiphelp.salesforce.com (opens in a new tab)
- Relationship Considerationshelp.salesforce.com (opens in a new tab)
- Relationships Overviewhelp.salesforce.com (opens in a new tab)
- Schema Builderhelp.salesforce.com (opens in a new tab)
- Schema Builder Considerationshelp.salesforce.com (opens in a new tab)
- Why can't a junction object's two master-detail fields both point to the same object?
- When should a requirement become a record type instead of a new custom object?
- Why does a new field built in Schema Builder need a field-level security review?
- Which custom field type can't be added in Schema Builder?
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 (14 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams