Salesforce Admin Section 2: Object Manager and Lightning App Builder

Lookup Relationship

• Add a field to an object that a user can use to find and link another object

• Ex: If you have a properties object, you can add a link to a contact object on the page.

• Can only have 1 record selected at a time

• For example: A property object can only have 1 owner, but a specific contact can own multiple property objects

• When to use

  • When you need to link 2 standard objects

  • When objects need to exist independently from each other

  • When you need optional relationships

  • When you need more than two parent relationships

  • You want to manually control record visibility and access

  • You want to retain the child record even if the parent is deleted

• Caveats

  • Can use lookup relationship on self.

  • Not required fields unless you make them.

  • Can enable “Delete this record also” in relationship settings

  • Child record has its own owner and sharing rules

  • Can’t use roll up summary fields unless you use workarounds like Apex triggers or Flow

Master-Detail Relationship

• A special type of relationship between objects (parent-child) where:

  • The relationship field is required on all detail records

  • The ownership and sharing of a detail record are determined by the master record

  • When a user deletes the master record, all detail records are deleted

  • You can create rollup summary fields on the master record to summarize the detail records

• Use sometimes, default to lookup

• The master side of the relationship controls some aspects of the Detail side.

• Detail record depends on the master record

• Use when

  • the child record must always be linked to a parent (required field)

  • You want cascading deletes

  • You want the child to inherit owner, sharing, and security

  • You need roll-up summary fields

  • You want to enforce strict data hierarchy and dependency

  • You’re working with custom objects

• Caveats

  • Can only use 2 master detail relationships on any given object

  • Cannot make a standard object the detail object, however, a custom object can be the master and detail

  • Do not use if you need relationship between 2 standard objects

  • Child inherits owner and sharing rules from parent.

  • Can only create roll-up summary fields on the master object

  • Cannot convert lookup to master if child records don’t have a parent assigned

  • Roll up summaries depend on the Master Detail Relationship

• How to delete a Master Detail relationship (no deleting)

  • Delete all Roll-Up summary fields on the master object

  • Ensure all child records have a parent

  • Change relationship type to lookup

  • Save and verify

Schema Builder

• A place where you can visualize the relationships between your objects.

• Like SQL schemas

• Can even create fields on the schema builder if needed

• Use for

  • Complex data

  • Quickly create or modify objects and fields

  • Can set Object Name / Label, Tab creation, Allow Reports, Allow Activities, Object Description, Enable for Customer Portal, and Deployment Status

• Caveats

  • Can be slow or unresponsive in orgs with lots of objects and fields

  • Some fields (like formula fields, managed package fields, or system fields) may not appear or be editable

  • You can’t set all field properties (like help text, validation rules, or FLS) use Object Manager for that

  • Cannot delete fields or objects

• What Schema Builder cannot do

  • Cannot set Field Tracking History, Search Layouts, Validation Rules, Record Type Assignments, FLS, Compact and Page Layouts, Business Processes

Object Manager

• A place where you can view all objects you have access to

Record Type

• Creates different types of records in a single object

• For example, in the account object, we can have a customer account or corporate account, and each of should have a different page layout

• Helps you choose:

  • Which page layout you want for each type

  • Allows you to create different processes for different types

  • Assign a different profile permission to each

  • For example, you can only allow your corporate users to create corporate accounts and nonprofit users to create nonprofit accounts

Page layout

• Controls what users can see and edit on a record page

• Controls fields, sections, buttons, related lists, mobile layout

• It does not control record access, field existence, and dynamic logic

• Assigned based on profile + Record type. Different users see different layouts for the same object

• drag n drop

Custom Fields

• A field that is not a standard field

• Can always remove standard fields from page layout if needed

• Cannot delete standard fields, only custom

• Can restore a deleted custom field within 15 days

• If you have trouble deleting a field, it probably is because that field is referenced somewhere else in salesforce, such as Apex custom code

Sales Process

• Used on Opportunities

• Controls which Stage values are available

• Assigned via Record Type

• Stage Values

  • Prospecting - Initial Outreach; Potential lead identified

  • Qualification - Lead confirmed as viable opportunity

  • Needs Analysis - Understanding customer requirements

  • Value Proposition - Presenting solution and benefits

  • Id. Decision Maker - Identifying who approves the deal

  • Perception Analysis - Addressing objections and concerns

  • Proposal/Price Quote - Formal quote or proposal sent

  • Negotiation/Review - Final terms being discussed

  • Closed Won - Deal successfully completed

  • Closed Lost - Deal not won

• You can define which stages you want to use in the process and connect it to a specific process.

Support Processes

• Processes used for cases

• controls which status values are available

• Assigned via Record Type

• Statuses

  • New - Case just created

  • Working - Case actively being handled

  • Escalated - Elevated due to urgency or complexity

  • On Hold - Waiting on customer or third party

  • Closed - Case resolved

Full Capability of Object Manager

• What it can do

  • Object Level Management

    • View and edit standard and custom objects

    • Create new custom objects

    • Rename custom objects and labels

    • Set object-level permissions

    • Enable/disable features like

      • Notes & Attachments

      • Chatter feed tracking

      • Search indexing

      • Record types

      • Business Processes

  • Field Management

    • Create, Edit, Delete fields (custom fields only)

    • Set FLS by profile

    • Define field types

    • Set default values and help text

    • Create validation rules, formula fields, dependent picklists

    • Track field history

  • Relationship Management

    • Create lookup and master-detail relationships

    • Define relationship behavior (cascade delete, required field)

    • Create external lookup and indirect lookup fields

    • Manage junction objects for many-to-many relationships

  • Page Layout and UI Customization

    • Create and manage record types

    • Assign picklist values per record type

    • Define business processes

    • Control page layout assignment by record type

  • Compact Layouts & Search Layouts

    • Define compact layouts

    • Customize search layouts (fields shown in search results, lookup dialogs)

  • Validation & Automation Access

    • Create and manage validation rules

    • Access related automation tools like:

      • Flow

      • Process Builder

      • Workflow Rules

      • Apex Triggers

  • Other Tools & Settings

    • Buttons, Links, Actions

    • Link Lightning App Builder for UI customization

    • View limits like max fields, relationships

    • View API name, object ID prefix, deployment status