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 relationship does more than store a link on one record: it also places a related list on the other record so users can see and add the connected records from the Related tab. Objects in a lookup relationship usually stand on their own and have their own tabs, while a master-detail detail record depends on its master and a junction object used for many-to-many typically does not need a tab. You then rename and customize those related lists so the page shows the other object's name and fields instead of the junction object's raw identity.