Section 3 · Object Manager and Lightning App Builder · 15% of exam
3.2 Fields, formulas, and field dependencies
Exam objective
Explain how to create, customize, and delete fields, including field types, relationship fields, roll-up summaries, formulas, and picklist dependencies. Field types determine what values can be stored and which operations are supported. Select a type that matches the data users enter and how it will be validated, displayed, searched, and reported. Relationship fields connect records; their relationship type affects requiredness and record behavior.
A roll-up summary aggregates values from related detail records in a master-detail relationship. A cross-object formula displays information from a related record where supported; it calculates a value rather than storing a separate copy. Dependent picklists constrain available values based on a controlling field, reducing invalid combinations. Before deleting a field, review references in formulas, validation rules, layouts, reports, automation, integrations, and managed dependencies. A field can sometimes be hidden, made read-only, or removed from layouts instead of deleted. Consider data retention and whether the value must remain available for history or reporting.
Additional concepts
Stored values and calculated values
A normal field stores user-entered or integrated data. A formula calculates a value from other fields and displays the result; it does not serve as an independently editable copy. A cross-object formula follows a supported relationship to reference information on another record.
Dependencies and deletion checks
A dependent picklist narrows values according to a controlling field. A roll-up summary aggregates related detail records in a master-detail relationship. Before deleting a field, review references in formulas, validation, automation, integrations, reports, and page configuration, then consider whether hiding or retiring it is safer.
A company needs a total of invoice detail amounts on each invoice. If the detail records have the required master-detail relationship, a roll-up summary may meet the need; a lookup relationship would not provide that same native roll-up behavior.
Key takeaways
- Field type controls storage and supported behavior.
- Roll-up summaries depend on master-detail; cross-object formulas reference related data.
- Check dependencies and data-retention effects before deleting a field.
