Lesson 4 of 18 · 8–12 min
Standard and Custom Objects
Choosing an existing standard object can preserve platform behavior and reduce maintenance.
Learning sequence · data model first, security layers next
- What CRM and Salesforce Do
- The Salesforce Ecosystem and Major Clouds
- Org, App, Object, Field, and Record
- Standard and Custom Objects
- Common Standard Objects
- Field Types and Data Quality
- Objects, Fields & Records
- Lookup vs Master-Detail
- Many-to-Many Relationships and Junction Objects
- Profiles, Permission Sets & Object Access
- Field-Level Security
- OWD and Least-Privilege Record Access
- Opening Access: Role Hierarchy, Sharing Rules, Public Groups & Apex Sharing
- Apex First Steps
- Variables and Collections
- SOQL and DML Basics
- Why Asynchronous Apex Exists
- REST Callout Introduction
Your focus
Prepare for Senior / Lead Roles
CHECKPOINT · Checkpoint
- Confirm the model quickly and identify architecture consequences.
Learning objective
Choose between a standard object, a custom object, and a relationship to an existing object.
The concept
Standard objects ship with Salesforce and support common CRM capabilities. Custom objects model organization-specific concepts and use an API name ending in __c. The decision depends on business meaning, lifecycle, security, reporting, automation, and integrations—not merely a similar label.
Worked example
Use Opportunity for a revenue deal. Add Delivery__c when delivery has its own lifecycle, owner, dates, and reporting rather than forcing those fields onto Opportunity.Define the entity and lifecycle. Compare them with standard object semantics. Reuse the standard object when the meaning fits; extend it with fields or relationships; create a custom object when the entity is genuinely distinct.
1.Business entity
2.Standard semantics fit?
3.Extend standard object
4.Create custom object
- Business entity connects to Standard semantics fit?
- Standard semantics fit? connects to Extend standard object: Yes
- Standard semantics fit? connects to Create custom object: No
Common mistake
Creating a custom object because the business uses a different word for a standard CRM concept.
Interview angle
Discuss semantics and platform behavior before storage convenience.
Pause and apply
Would a property inspection be fields on Opportunity or its own object? What lifecycle evidence decides?
Official references
- Salesforce Trailhead: Understand Custom & Standard Objects (opens in a new tab)
- Salesforce Trailhead: Create Custom Objects (opens in a new tab)
Reviewed 2026-09-23. Examples are illustrative; no code is executed here.
Key takeaways
- Reuse standard semantics when they fit.
- Create custom objects for distinct business entities and lifecycles.
Practice next
No linked assessment is available for this lesson. Use the pause-and-apply question to check your reasoning.
Reading these lessons does not yet save completion. Challenge results continue to provide assessment evidence.