Checklist progress
0/316Learned
Platform App Builder
Study Checklist
Checklist progress
0/316Learned
Given a scenario, determine the appropriate data model.
0/14
Given a scenario, explain the capabilities of the various relationship types and the implications of each on record access, user interface, and reporting.
0/14
Master-detail cascade delete and restore
Learn this conceptLookup parent-delete field behaviors
Learn this conceptMaster-detail child reparenting
Learn this conceptRecord access for master-detail versus lookup children
Learn this conceptMaster-detail Sharing Setting on the relationship field
Learn this conceptRelated lists and object tabs for relationships
Learn this conceptStandard report types by relationship type
Learn this conceptCustom report types for related objects
Learn this conceptJunction object primary master effects
Learn this conceptMultilevel master-detail relationships
Learn this conceptLookup filters on relationship fields
Learn this conceptConverting lookup and master-detail relationships
Learn this conceptExternal lookup versus indirect lookup
Learn this conceptGiven a scenario, determine the considerations when selecting or changing a field data type.
0/19
Given a scenario, determine the options and considerations when importing and exporting data, including the capabilities of external data sources.
0/9
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform App Builder studiers. 592 members and growing.
A junction object is a custom object with two master-detail relationships that connect two other objects so each side can link to many records on the other. The first master-detail relationship you create is the primary relationship, and it controls the junction record’s look and feel plus which master supplies inherited ownership and division. Those inherited values stay hidden while the master-detail relationships exist and only matter if you later remove both of them.