Memory hook: Data structure, business process and screen layout are different layers.
Must remember
Standard objects model common CRM entities; custom objects represent additional business data. Records are rows and fields store attributes/relationships. Lookup relationships provide flexible links; master-detail relationships give tighter lifecycle/ownership behavior, including supported roll-up summaries and cascade implications. A junction object commonly represents many-to-many relationships.
Formula fields calculate derived values; cross-object formulas can reference supported parent relationships. Roll-up summaries aggregate eligible detail records under supported relationships. A formula is not a stored manual input, and a lookup alone does not provide every native master-detail roll-up behavior. Dependent picklists constrain choices using a controlling field.
Record types select available business processes/picklist values and participate in page-layout assignment. A sales/support process defines permitted stages/statuses for its use case. Page layouts arrange fields/actions; Lightning App Builder composes pages and component visibility. Dynamic visibility improves experience but does not replace field/record security.
Object-specific quick actions operate in a record context; global actions can be offered without that specific context. List views provide saved filters and selected columns; sharing a view does not automatically grant access to its underlying records. Schema Builder visualizes objects and relationships but does not validate every business modeling decision.
Before deleting/changing a field, inspect formulas, automation, reports, integrations and stored values. Data-type conversion or relationship changes can lose information or invalidate dependencies. Test in a suitable nonproduction environment and preserve a recovery path before structural changes.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Aggregate detail amounts on a parent | Eligible roll-up summary/master-detail design. |
| Different stage choices for business processes | Record types plus the appropriate process/picklist configuration. |
| Different page composition by context | Lightning App Builder with deliberate activation/visibility. |
Traps
- Record type is not a replacement for access control.
- A page-layout change does not change every API/data behavior.
Active recall
1. Lookup versus master-detail?
Flexible association versus a tighter dependent relationship with ownership/lifecycle implications.
2. What is a junction object for?
Representing a many-to-many relationship.
3. Formula versus roll-up summary?
A calculated expression versus aggregation over eligible related detail records.
4. Why inspect dependencies before deletion?
Automation, reports and integrations may rely on the field.
5. What does a record type help vary?
Business process, picklist choices and associated page layout.