TECH **Salesforce Administrator: Standard Objects & Relationships – Zero-Fluff Study Guide**

Salesforce Administrator: Standard Objects & Relationships – Zero-Fluff Study Guide

1. What This Is & Why It Matters

You’re a Salesforce Administrator inheriting a messy org where sales reps complain about duplicate leads, support agents can’t track customer history, and managers ask for reports that don’t exist. The root cause? Misconfigured standard objects and broken relationships.

Standard objects (Account, Contact, Lead, Opportunity, Case) are the backbone of Salesforce. If you don’t understand how they work and relate to each other, you’ll: - Break data integrity (e.g., orphaned contacts, duplicate accounts).
- Fail audits (e.g., missing case escalation rules).
- Waste time manually fixing reports instead of automating them.

Real-world scenario:
Your sales team converts leads into opportunities, but the data is inconsistent—some opportunities lack contacts, others have duplicate accounts. Your CEO asks for a report on "closed-won deals by customer," but the data is scattered. You need to fix relationships, enforce validation rules, and set up automation—fast.

This guide gives you immediate, actionable steps to master standard objects and their relationships—so you can clean up data, automate workflows, and pass the Salesforce Admin exam without memorizing fluff.

2. Core Concepts & Components

? Account

• Definition: A company or organization you do business with (e.g., "Acme Corp").
• Production insight: If you don’t enforce duplicate rules, sales reps will create multiple accounts for the same company, breaking reports and automation.

? Contact

• Definition: A person associated with an Account (e.g., "John Doe at Acme Corp").
• Production insight: Contacts must be linked to an Account—orphaned contacts (no Account) cause reporting gaps and automation failures.

? Lead

• Definition: A potential customer (unqualified prospect) before they become an Opportunity.
• Production insight: If you don’t set up lead assignment rules, leads sit unassigned, and sales reps miss deals.

? Opportunity

• Definition: A potential sale (e.g., "Acme Corp – $50K ERP Software Deal").
• Production insight: Opportunities must be linked to an Account (and optionally a Contact). Missing links break pipeline reports.

? Case

• Definition: A customer issue or support request (e.g., "Acme Corp – Login Error").
• Production insight: Cases must be linked to an Account (and optionally a Contact). Without this, support agents can’t track customer history.

? Lookup Relationship

• Definition: A loose link between two objects (e.g., Contact → Account). Deleting the parent doesn’t delete the child.
• Production insight: If you delete an Account, its Contacts become orphans—use validation rules to prevent this.

? Master-Detail Relationship

• Definition: A strict parent-child relationship (e.g., Opportunity → Account). Deleting the parent deletes the child.
• Production insight: Use this for dependent data (e.g., Opportunity Line Items). If you delete an Opportunity, its line items vanish.

? Lead Conversion

• Definition: Turning a Lead into an Account, Contact, and Opportunity.
• Production insight: If mapping rules are wrong, data ends up in the wrong fields (e.g., "Company" → "First Name").

? Record Types

• Definition: Different "flavors" of the same object (e.g., "Customer Account" vs. "Partner Account").
• Production insight: Without page layouts per record type, users see irrelevant fields, slowing them down.

3. Step-by-Step Hands-On: Fixing Broken Relationships

Prerequisites

✅ Salesforce org (Developer Edition or Sandbox).
✅ System Administrator access.
✅ A messy dataset (or create one for testing).

Task: Clean Up Orphaned Contacts & Enforce Account Linking

Problem: Your org has Contacts not linked to Accounts, breaking reports.

Step 1: Find Orphaned Contacts

1. Go to Setup → Object Manager → Contact → Fields & Relationships.
2. Click New → Formula (Checkbox).
3. Name: Is_Orphaned
4. Formula:
   plaintext
ISBLANK(AccountId)
5. Save.
6. Go to Reports → New Report → Contacts & Accounts.
7. Add filter: Is_Orphaned = True.
8. Run report—these are your orphaned contacts.

Step 2: Bulk Reassign Orphaned Contacts

1. Export the report (CSV).
2. Use Data Loader (or Dataloader.io) to update AccountId for these contacts.
3. Alternative: Use Mass Update in List View (if < 200 records).

Step 3: Prevent Future Orphans

1. Go to Setup → Object Manager → Contact → Validation Rules.
2. Click New.
3. Rule Name: Account_Required
4. Error Condition Formula:
   plaintext
ISBLANK(AccountId)
5. Error Message: "Every Contact must be linked to an Account."
6. Save.

Step 4: Test the Fix

1. Try creating a Contact without an Account—you should get an error.
2. Run the Is_Orphaned report again—it should now be empty.

4. ? Production-Ready Best Practices

? Security & Data Integrity

• Enforce Account-Contact linking (Validation Rule: ISBLANK(AccountId)).
• Use Record Types to separate "Customer" vs. "Partner" Accounts.
• Set up Duplicate Rules (e.g., "Acme Corp" vs. "Acme Corporation").

? Cost & Performance

• Avoid excessive Lookup fields (they slow down reports).
• Use Master-Detail only when necessary (deleting a parent deletes children).
• Archive old Cases (use Case Archiving or Big Objects).

? Reliability & Maintainability

• Standardize naming conventions (e.g., "Acme Corp" not "Acme").
• Use Page Layouts per Record Type (e.g., "Support Case" vs. "Billing Case").
• Automate Lead Assignment (use Assignment Rules or Flow).

? Observability

• Monitor orphaned records (Scheduled Report: "Orphaned Contacts").
• Track Case escalations (Dashboard: "Cases > 7 Days Old").
• Log Opportunity changes (Field History Tracking).

5. ⚠️ Common Mistakes & Traps

6. ? Exam/Certification Focus

Typical Question Patterns

1. "Which object is required when converting a Lead?"
2. ✅ Account, Contact, Opportunity (all three).

3. ❌ Just "Account" (trick answer).

4. "What happens if you delete an Account with a Master-Detail relationship to Opportunities?"

5. ✅ Opportunities are deleted.

6. ❌ "Opportunities become orphans" (that’s Lookup, not Master-Detail).

7. "How do you prevent users from creating Contacts without Accounts?"

8. ✅ Validation Rule: ISBLANK(AccountId)
9. ❌ "Use a Lookup Filter" (wrong—Lookup Filters restrict choices, not enforce existence).

Key ⚠️ Trap Distinctions

• Lookup vs. Master-Detail:
• Lookup = Loose (deleting parent doesn’t delete child).
• Master-Detail = Strict (deleting parent deletes child).
• Lead Conversion:
• Account = Company name.
• Contact = Person’s name.
• Opportunity = Potential deal.

7. ? Hands-On Challenge (With Solution)

Challenge:
Your org has Leads with missing "Company" fields. When converted, they create Accounts named "Unknown." Fix this so Leads must have a Company before conversion.

Solution:
1. Go to Setup → Object Manager → Lead → Validation Rules.
2. New Rule: Company_Required 3. Formula:
plaintext
ISBLANK(Company) 4. Error Message: "Leads must have a Company before conversion." 5. Save.

Why it works:
- Salesforce blocks conversion if the validation rule fails.
- Forces users to fill in Company before converting.

8. ? Rapid-Reference Crib Sheet

Commands & Shortcuts:
- Find orphaned records: SELECT Id FROM Contact WHERE AccountId = NULL - Bulk update via Data Loader: Update AccountId in CSV.
- Lead conversion mapping: Setup → Lead Settings → Map Lead Fields.

9. ? Where to Go Next

1. Salesforce Trailhead: Standard Objects
2. Salesforce Help: Lead Conversion
3. Salesforce Developer Docs: Relationships
4. Book: Salesforce CRM: The Definitive Admin Handbook (Paul Goodey).

Final Tip:

Standard objects are the foundation—master them, and everything else (automation, reports, security) becomes easier. Start by auditing your org’s relationships today. ?