Object Manager and Lightning App Builder · Topic 2 of 2
Fields, Page Layouts, Lightning Pages and Actions
Salesforce customization: creating and deleting fields, page layouts, Lightning record pages and Dynamic Forms, compact layouts and quick actions.
- 4 min
- Remove references before deleting a field; deleted fields can be restored for 15 days.
- Page layouts are assigned by profile and record type; Lightning pages by app, record type and profile.
- Dynamic Forms and component visibility show content conditionally.
What it is
Fields store the details of each record. Page layouts and Lightning record pages decide how fields, related lists and actions appear. Actions let users create or update records quickly. Knowing what happens when you change or delete fields is a common exam topic.
How it works
Creating fields
- Choose the field type carefully: text, number, currency, date, picklist, multi-select picklist, checkbox, formula, lookup, master-detail and more.
- Set field-level security (who can see and edit it) and add it to page layouts.
- Dependent picklists limit the values of one picklist based on another (the controlling field).
- Formula fields calculate values, including cross-object formulas that read fields from parent records.
Deleting and changing fields
| Situation | Implication |
|---|---|
| Field used in a formula, roll-up summary, validation rule, flow or other reference | You must remove those references before you can delete it |
| Field is a controlling field in a picklist dependency | Review the dependency first; a dependency can be deleted on its own without deleting either field or its data |
| Deleted field | Moves to the Deleted Fields list and can be restored with its data for 15 days; restored formula fields stay disabled until edited and saved |
| Changing a field type | Can cause data loss, for example text to number |
| Deleting a relationship field | Affects related records, roll-ups and reports |
Page layouts and Lightning pages
| Feature | Purpose |
|---|---|
| Page layout | Arranges fields, related lists and buttons; assigned by profile and record type |
| Lightning record page | Built in Lightning App Builder; arranges components such as Highlights, Path and related lists; assigned by app, record type and profile |
| Dynamic Forms | Places individual fields and sections on the Lightning page and shows or hides them with visibility rules |
| Component visibility | Shows a component only when conditions are met, such as a field value or device |
| Compact layout | Sets the key fields shown in the highlights panel and on mobile |
A required field on a page layout is only required in that layout; a field made required in its definition is required everywhere.
Quick actions and global actions
| Action | Where it works |
|---|---|
| Object-specific action | On a record, creating related records or updating the record, with fields pre-filled |
| Global action | Anywhere, such as the global actions menu, creating records not tied to a parent |
A worked example: support agents need a "Priority Reason" field that appears only when Priority is High. Create the field, add it to the Lightning record page with Dynamic Forms, and set a visibility rule so it shows only when Priority equals High.
Hiding a field on a page layout does not secure it. Users can still see it in reports or list views if field-level security allows. Use field-level security to restrict access.
How the exam asks about this
- "Why can't the administrator delete a field?" It's referenced, for example in a formula or roll-up summary.
- "Show a field only when another field has a certain value." Dynamic Forms with a visibility rule.
- "Let users create a contact from an account with fields pre-filled." An object-specific quick action.
What to remember for the exam
- Remove references before deleting a field; deleted fields can be restored for 15 days.
- Page layouts are assigned by profile and record type; Lightning pages by app, record type and profile.
- Dynamic Forms and component visibility show content conditionally.
- Compact layouts control the highlights panel and mobile header.
- Object-specific actions work on a record; global actions work anywhere.
Changing a field's data type can lose data. Export the data before converting field types.
Common mistakes
Using a page layout to hide sensitive data. Use field-level security.
Making a field universally required when only one process needs it. Required on the layout may be enough.
Forgetting to add new fields to layouts. Users won't see them.
Check yourself
Why might an administrator be unable to delete a custom field?
The field is referenced elsewhere, such as in a formula, roll-up summary, validation rule or flow.
What do Dynamic Forms add to a Lightning record page?
The ability to place individual fields and sections and show or hide them with visibility rules.
What is the difference between an object-specific action and a global action?
An object-specific action works on a specific record; a global action works anywhere and isn't tied to a record.
Topic 2 of 2 in Object Manager and Lightning App Builder
Test yourself on Object Manager and Lightning App Builder
The full Salesforce Platform Administrator question bank has 650 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Salesforce. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.