3.4 Schema Builder & Data Architecture Visualization
Key Takeaways
Schema Builder is a visual design environment that renders an interactive entity-relationship diagram (ERD) of all standard and custom objects in an org.
App builders can drag and drop custom objects, custom fields, and relationship fields directly onto the Schema Builder canvas for real-time schema construction.
Custom fields created in Schema Builder default to visible and editable for all internal profiles before explicitly managing field permissions.
Fields created via Schema Builder are never automatically added to Page Layouts or Lightning Record Pages and must be manually placed using page editors.
Relationship lines in Schema Builder are color-coded: Master-Detail relationships appear as red lines, while Lookup relationships appear as blue lines.
Schema Builder & Data Architecture Visualization
Important
Schema Builder provides a visual design canvas to view, model, and modify the database schema of a Salesforce organization. While it dramatically accelerates schema prototyping and relationship analysis, app builders must know its administrative limitations—especially regarding Field-Level Security and page layouts—for the Platform App Builder exam.
Navigating Object Manager across dozens of separate setup pages to create objects, add fields, and link relationships can be slow during rapid prototyping. Schema Builder solves this by providing a unified, interactive Entity-Relationship Diagram (ERD) canvas. Located directly within Setup, Schema Builder visualizes standard and custom objects, their individual fields, and the complex web of relationships connecting them.
Visual Inspection & Modeling Capabilities
When Schema Builder opens, it presents a dynamic two-dimensional canvas alongside a control sidebar containing two primary tabs: Objects and Elements.
1. The Objects Palette & Filtering
- Selectable Viewing: App builders can filter the canvas to show All Objects, Selected Objects, Standard Objects, Custom Objects, or System Objects. This prevents visual overload in enterprise orgs containing hundreds of database entities.
- Auto-Layout & Custom Positioning: Clicking "Auto-Layout" reorganizes the ERD automatically, but users can also drag object cards to custom coordinates. Salesforce saves individual layout positions per administrator session.
- Relationship Line Conventions:
- Red Lines: Represent Master-Detail Relationships. Clicking or hovering over the line highlights the link between the master entity and detail entity.
- Blue Lines: Represent Lookup Relationships.
2. On-Canvas Declarative Creation
From the Elements tab, app builders can drag components directly onto the diagram surface:
- Custom Objects: Dragging the "Object" element onto the canvas opens a modal dialog to define the object label, plural label, object name (API name), record name (Text or Auto-Number), and deployment status (In Development or Deployed). Upon clicking Save, the object card immediately renders on the canvas.
- Custom Fields: Any standard field type (Text, Number, Date, Currency, Checkbox, Picklist, etc.) can be dragged from the Elements palette directly onto an existing object card. The builder configures label, length, decimals, and required attributes, and the field instantly appears on the card.
- Relationship Fields: Dragging a Lookup Relationship or Master-Detail Relationship element onto a child object card opens the relationship configuration wizard, automatically linking the two entities with a visible connector line upon completion.
Critical Administrative Limitations & Exam Traps
While Schema Builder is exceptionally powerful for rapid data architecture modeling, it bypasses several standard administration setup gates. These omissions represent critical exam test points:
+-----------------------------------------------------------------------------------+
| SCHEMA BUILDER VS. OBJECT MANAGER |
+-----------------------------------------------------------------------------------+
| FIELD-LEVEL SECURITY (FLS): |
| • Schema Builder: Does not prompt for FLS in the field creation dialog. |
| Defaults to Visible & Editable for ALL internal profiles. |
| • Object Manager: Explicit step-by-step FLS configuration per profile. |
+-----------------------------------------------------------------------------------+
| PAGE LAYOUT PLACEMENT: |
| • Schema Builder: Fields are NEVER automatically added to page layouts. |
| Must be added manually in Page Layout editor or Lightning App Builder. |
| • Object Manager: Offers a prompt to automatically add field to page layouts. |
+-----------------------------------------------------------------------------------+
| CUSTOM TAB CREATION: |
| • Schema Builder: Does NOT launch the Custom Tab wizard after object creation. |
| • Object Manager: Checkbox allows immediate launch of Tab Wizard. |
+-----------------------------------------------------------------------------------+
1. The Field-Level Security (FLS) Trap
When an administrator creates a custom field through the standard Object Manager wizard, Step 3 explicitly prompts the administrator to set Field-Level Security for each profile (determining whether the field is Visible, Hidden, or Read-Only).
In contrast, Schema Builder does not prompt for Field-Level Security. Instead, Salesforce automatically assigns default FLS:
- The field is set to Visible and Editable (Read/Write) for all standard and custom internal profiles.
- The field is set to Read-Only for profiles with restricted read permissions (like the standard Read Only profile).
- The field is Hidden for external Community or Guest user profiles.
Warning
If sensitive data (such as executive compensation, credit scores, or security tokens) is created using Schema Builder, it will immediately be exposed to all internal users with object access. Immediately configure access through Manage Field Permissions on the Schema Builder field, or through Object Manager/permission administration.
2. Page Layout and Lightning Page Omission
When an app builder creates custom fields inside Schema Builder, the fields are never automatically placed on any Page Layouts or Lightning Record Pages.
- End users navigating to record detail pages will not see the newly created fields, even though the fields exist in the database and API.
- The administrator must manually open the Page Layout editor or Lightning App Builder and drag the new fields onto the designated page sections.
3. Missing Custom Tab Creation
When creating a custom object in Schema Builder, the wizard does not include the option to launch the Custom Tab creation wizard. As a result, the object cannot be accessed from the App Launcher or added to navigation bars until an administrator navigates to Setup > User Interface > Tabs and manually configures a new custom tab.
When to Use Schema Builder vs. Object Manager
Architects must select the appropriate declarative tool based on the project phase and security requirements:
| Operational Requirement | Recommended Tool | Rationale |
|---|---|---|
| Visualizing Existing ERD | Schema Builder | Displays full relationship graph, foreign keys, and object dependencies at a glance. |
| Rapid Multi-Object Prototyping | Schema Builder | Allows instant drag-and-drop creation of objects, fields, and relationships on one canvas. |
| Strict Security / Sensitive Fields | Object Manager | Enforces granular profile-by-profile Field-Level Security configuration during creation. |
| Immediate UI Page Deployment | Object Manager | Offers steps to add new fields into active page layouts during the creation wizard. |
| Configuring Custom Tabs | Object Manager | Offers a direct checkbox to launch the Custom Tab wizard immediately upon object save. |
| Auditing Relationship Types | Schema Builder | Color-coded lines (Red = Master-Detail, Blue = Lookup) make structural audits instantaneous. |
An app builder uses Schema Builder to quickly create three new custom fields on the Opportunity object during a data modeling workshop. Later, sales representatives report that they cannot see the new fields when creating or editing Opportunity records. What is the reason for this behavior?
Fields created in Schema Builder are kept in 'Draft' mode until the entire schema is published.
Fields created via Schema Builder are not automatically added to Page Layouts or Lightning Record Pages.
Schema Builder automatically sets the Field-Level Security of all newly created fields to Hidden for all profiles.
The Opportunity object must be set from 'In Development' to 'Deployed' before fields appear.
A business analyst creates a new custom field called Executive_Bonus__c on a custom Compensation__c object using Schema Builder. What is the default Field-Level Security (FLS) assigned to this new field?
The field is hidden from all users until an administrator manually configures FLS in Object Manager.
The field is visible and editable only to the System Administrator profile.
The field is visible and editable for all internal user profiles with object access.
The field inherits the exact FLS settings of the object's primary Record Name field.
Universal Containers is conducting an architectural review of a complex Salesforce org with dozens of custom objects. The lead architect wants to quickly identify all Master-Detail relationships across the custom data model without inspecting each object individually in Object Manager. How can Schema Builder facilitate this review?
By executing a SOQL query in the Developer Console to export all relationship schema definitions.
By running an automated Schema Builder report grouped by Relationship_Type__c.
By opening the Field Dependency matrix within Setup and filtering on Master-Detail.
By opening Schema Builder and visually inspecting the canvas for red connector lines linking objects.
Sections you finish are checked off in the contents.