Schema Builder

5 minutes 5 Questions

Schema Builder is a visual, drag-and-drop tool in Salesforce Setup that lets administrators view, design, and modify the data model of an org in a single interactive canvas. For a Platform Administrator II candidate studying Objects and Applications, it is an important productivity and documentation tool because it displays standard and custom objects, their fields, and the relationships (lookup and master-detail) between them as a diagram, making complex schemas easier to understand and explain to stakeholders. Key capabilities include: (1) Viewing objects and fields—you can select which objects appear on the canvas, filter to show only required fields or system fields, and hover over relationship lines to see details like relationship type and field names. (2) Creating objects—new custom objects can be added directly from the Elements tab, including label, plural label, record name, and data type. (3) Creating fields—many field types (Text, Number, Checkbox, Date, Picklist, Formula, Lookup, Master-Detail, etc.) can be dragged onto an object; the field is created immediately without the standard multi-step wizard. (4) Editing—you can edit field properties, change descriptions, and use Quick Find to locate objects. (5) Auto-layout—arranges objects neatly, and layouts persist per user. Important exam-relevant nuances: fields created in Schema Builder are not automatically added to page layouts and field-level security defaults must still be reviewed; some field types such as Roll-Up Summary and Geolocation are not available via Schema Builder; you cannot set lookup filters or delete relationships directly from the canvas in all cases; and you cannot export the diagram natively (screenshots or third-party tools are typically used). Schema Builder also does not create tabs, page layouts, or profiles. Best practice: use Schema Builder for rapid prototyping, data model documentation, and onboarding, while using standard Object Manager for detailed configuration like validation rules, page layouts, and field history tracking.

Schema Builder in Salesforce: A Complete Guide for the Advanced Administrator Exam

Why Schema Builder Matters
Every Salesforce org is built on a data model: objects, fields, and the relationships that connect them. As an Advanced Administrator you are expected to design, extend, and troubleshoot that model quickly and accurately. Schema Builder is the tool Salesforce provides to visualize and edit the data model in one place, so questions about it appear in the Advanced Objects and Applications section of the exam. Understanding what Schema Builder can and cannot do helps you choose the right tool in real projects and eliminates distractor answers on test day.

What Schema Builder Is
Schema Builder is a dynamic, drag-and-drop interface, found under Setup > Objects and Fields > Schema Builder, that displays an entity-relationship diagram (ERD) of standard and custom objects in your org. Each object appears as a box listing its fields, and lines between boxes represent lookup and master-detail relationships. Unlike a static diagram, Schema Builder reads live metadata, so it always reflects the current state of the org, including fields and objects created elsewhere in Setup.

Schema Builder is both a viewer and an editor. You can simply inspect how objects connect, or you can create new custom objects, custom fields, and relationships directly on the canvas without leaving the page.

How Schema Builder Works

1. Viewing the schema
The left panel has two tabs: Objects and Elements. On the Objects tab you select which standard and custom objects to display. A filter lets you show All Objects, Selected Objects, Standard Objects, Custom Objects, or System Objects, and a quick-find box searches by name. Objects you check appear on the canvas; unchecking removes them from view (it does not delete them). You can drag objects around, zoom in and out, and use the small map in the corner to navigate large diagrams. Choose Auto-Layout to let Salesforce arrange the objects automatically.

2. Reading the diagram
Each object box shows its fields. You can toggle Show Element Names to display API names instead of labels and choose to hide or show relationships. Relationship lines indicate the type: lookup relationships and master-detail relationships are drawn with distinct line styles, and hovering over a line highlights the two objects involved. Required fields are shown in bold, which helps when reviewing data-quality rules.

3. Creating objects and fields
On the Elements tab you drag items onto the canvas. Dragging Object onto empty space opens a dialog to create a custom object (label, plural label, object name, record name and data type, and options such as Allow Reports, Allow Activities, Track Field History, Deployment Status). Dragging a field type (Text, Number, Picklist, Checkbox, Date, Formula, Roll-Up Summary, Lookup Relationship, Master-Detail Relationship, and so on) onto an existing object opens the field creation dialog. Dragging a Lookup or Master-Detail onto an object and choosing the related object draws the relationship line immediately.

4. Editing and deleting
Clicking a field on an object lets you edit its properties, and you can delete custom fields and custom objects from the canvas. Note that Schema Builder enforces the same rules as standard Setup: you cannot delete standard objects or standard fields, and you cannot delete a field referenced by other metadata until the dependency is removed.

5. What Schema Builder does not do
This is where exam questions often focus. Schema Builder does not let you:
- Set field-level security or profile permissions for the new field (fields created here are by default visible and editable to all profiles unless you later adjust FLS, and they are not automatically added to page layouts).
- Add fields to page layouts, record types, or Lightning pages.
- Create validation rules, workflow, flows, triggers, or approval processes.
- Create custom objects via import or export of the diagram; the diagram itself cannot be exported as an image natively.
- Define sharing rules, roles, or org-wide defaults.

Key Facts to Memorize
- Location: Setup > Objects and Fields > Schema Builder (available in Lightning and Classic).
- Shows standard, custom, and system objects; filters control what is displayed.
- Creating a field in Schema Builder skips the field-level security and page layout steps of the standard wizard, so follow up in Object Manager.
- Relationship lines distinguish lookup vs. master-detail; a master-detail field created here makes the object a detail and inherits sharing from the master.
- Schema Builder reflects live metadata; there is no save step for layout changes to the metadata itself because object and field creation is committed immediately.
- Useful for documentation, onboarding, impact analysis before deleting a field, and rapid prototyping of new data models.
- Alternative tools to recognize: Object Manager (full field wizard), Data Loader (data, not schema), Lightning App Builder (pages, not data model), Developer Console and Metadata API (code-based schema work).

Exam Tips: Answering Questions on Schema Builder

Tip 1 - Match the requirement to visualization. If a scenario says a user needs to see how objects relate, understand the data model, or review relationships before a project, Schema Builder is almost always the intended answer. Words like diagram, visual, relationships, and ERD are strong signals.

Tip 2 - Know what is created versus what is skipped. A common question describes an admin who created a field in Schema Builder and users cannot see it. The correct answer involves field-level security and page layout assignment, which Schema Builder does not handle. Do not pick answers suggesting the field was not saved or that Schema Builder cannot create fields.

Tip 3 - Eliminate distractors that confuse tools. If an option says Schema Builder creates validation rules, sharing rules, reports, or page layouts, it is wrong. If an option says Object Manager shows a graphical relationship map, it is wrong. Keep the boundaries clear.

Tip 4 - Watch for relationship type questions. When a scenario involves choosing lookup vs. master-detail while building in Schema Builder, apply normal relationship rules: master-detail for tightly coupled records, roll-up summaries, and inherited sharing; lookup for optional or loosely related records.

Tip 5 - Remember it is live and immediate. Objects and fields created in Schema Builder exist instantly in the org and appear in Object Manager. Questions implying a separate deployment or activation step for Schema Builder changes are describing a different tool.

Tip 6 - Use it for impact analysis scenarios. If the scenario asks how an admin can quickly determine which objects would be affected by deleting a custom object, viewing its relationships in Schema Builder is a valid, efficient answer, alongside checking field dependencies in Object Manager.

Tip 7 - Read for the word custom. Schema Builder can create and delete only custom objects and fields. Any answer suggesting standard objects or standard fields can be deleted there is incorrect.

Tip 8 - Prefer the simplest declarative tool. The Advanced Administrator exam rewards declarative, low-effort solutions. When Schema Builder meets the need, it will usually beat answers involving code, the Metadata API, or third-party apps.

Quick Self-Check
Ask yourself: Can I describe how to display only custom objects? Can I explain why a new Schema Builder field is invisible to users? Can I list three things Schema Builder cannot do? If you can answer these confidently, you are ready for Schema Builder questions on the exam.
Test mode:
Start practice test

Admin II - Schema Builder Example Questions

Test your knowledge of Schema Builder

Question 1

Universal Containers needs to track Consultants and Projects so that each consultant can work on many projects and each project can have many consultants. Each project record must also show the total hours logged across all of its assignments. The administrator will build the data model in Schema Builder and wants sales users to see the new fields on records. Which design should the administrator create?

Correct Answer: Junction object with two master-detail fields and a roll-up, then update page layouts

A junction object with two master-detail fields creates the many-to-many relationship, and a roll-up summary field on Project can total hours from the assignment records. Fields created in Schema Builder are not automatically added to page layouts, so the administrator must update the layouts manually.
Two lookup fields cannot support a native roll-up summary, which requires a master-detail relationship. A single master-detail field from Consultant to Project only models one-to-many, not many-to-many. Expecting the new fields to appear on layouts automatically is wrong because Schema Builder does not add fields to page layouts.
Key concept: Many-to-many junction objects, roll-up summary requirements, and Schema Builder layout behavior.

Question 2

Cloud Kicks needs to link Shoes and Athletes so that each shoe can be endorsed by many athletes and each athlete can endorse many shoes. Each Shoe and Athlete record must show the total endorsement value. Users will add endorsements from the Athlete record page. The administrator plans to build the solution in Schema Builder in a sandbox and then deploy it. Which plan should the administrator recommend to meet every requirement?

Correct Answer: Create two master-detail fields and both roll-ups in Schema Builder, then add the related list to the Athlete layout

A junction object with two master-detail fields creates the many-to-many link and allows roll-up summary fields on both Shoe and Athlete. Because Schema Builder does not add new relationships or related lists to page layouts, the administrator must add the related list to the Athlete layout manually so users can enter endorsements there.
Two lookup fields do not support native roll-up summary fields. A master-detail to Shoe with a lookup to Athlete allows a roll-up only on Shoe, so Athlete cannot show the total. Relying on a default related list fails because Schema Builder does not place one on the layout.
Key concept: a junction object with two master-detail relationships, roll-up summaries, and Schema Builder's page layout limitation.

Question 3

Northern Trail Outfitters tracks gear rentals in a spreadsheet. A team lead asks the administrator for a new custom object whose fields mirror the spreadsheet columns. Every existing row must be available as a record, and the whole request should be handled in a single guided process. The administrator plans to open Schema Builder to start the work. What should the administrator do instead?

Correct Answer: Upload the spreadsheet to Lightning Object Creator to generate the object and records

Lightning Object Creator takes an uploaded spreadsheet and, in one guided flow, creates a custom object with fields mapped from the columns and imports every row as a record.
Modeling in Schema Builder and then using the Data Import Wizard splits the work into two separate tools, so it is not a single guided process. Change sets deploy metadata only, never records. Lightning Object Creator cannot import rows into an object already built in Schema Builder, because it always creates a new object from the spreadsheet.
Key concept: Lightning Object Creator builds a custom object and its records directly from a spreadsheet.

More Schema Builder questions
60 questions (total)
Start 60 question test

Other Objects and Applications concepts

Compact Layouts and PathConverting Between Lookup and Master-DetailCross-Object Formula FieldsDynamic ActionsDynamic FormsJunction Objects and Many-to-Many RelationshipsLightning App Builder Record PagesLightning Apps in App ManagerLightning Console Apps, Split View and Utility BarLightning Page Assignment by App, Record Type and ProfileLightning Page Performance and the Analyze ButtonLookup Relationships and Lookup FiltersMaster-Detail RelationshipsObject Creator from a SpreadsheetRecord Types and Business ProcessesRelated Lists and Related List ConfigurationRoll-Up Summary FieldsStandard Lightning Page Components and Visibility Rules
All Objects and Applications questions · Admin II practice test