Unlock the power of custom data modeling in Salesforce!
🌟 Introduction
Welcome to Day 3 of your Salesforce journey! After exploring Standard Objects (Accounts, Contacts, Leads), today we dive into Custom Objects – the backbone of tailoring Salesforce to your business needs. Let’s build your first custom object!
🔄 Recap: Objects in Salesforce
Definition:
“Objects are database tables in Salesforce that store records (e.g., customer data).”
Types:
- Standard Objects: Pre-built by Salesforce (e.g.,
Account,Contact).- 🛠️ Cannot be created/deleted.
- Custom Objects: Created by YOU for unique business needs.
- 🧩 Can be created/deleted.
Icon: 📊 (Table Structure)
Thumb Rule:
“If it’s Standard, Salesforce owns it. If it’s Custom, YOU own it!”
🧩 Deep Dive: Custom Objects
Why Create Custom Objects?
- Solve unique business problems (e.g., tracking job applications, inventory).
- Extend Salesforce beyond CRM (HR, Recruitment, Project Management).
Key Terminology
| Term | Description |
|---|---|
| Label | Singular name (e.g., “Position”). |
| Plural Label | Name displayed in tabs/reports (e.g., “Positions”). |
| Object Name | Auto-generated API name (e.g., Position__c). Best Practice: Don’t change! |
| Record Name | Default field for record identification (e.g., “Position Name”). |
🔧 Step-by-Step: Creating a Custom Object
Scenario: Build a “Position” object for a Recruitment App.
Step 1: Navigate to Setup
- Path:
Setup→Object Manager→Create→Custom Object.
https://img.icons8.com/ios/50/gear.png
Step 2: Configure Basic Settings
| Field | Value | Emoji |
|---|---|---|
| Label | Position |
🏷️ |
| Plural Label | Positions |
📑 |
| Object Name | Position__c (auto) |
🤖 |
| Record Name | Position Name |
🔤 |
| Data Type | Text (default) |
📝 |
💡 Pro Tip: Use Auto Number for IDs (e.g.,
POS-001) later!
Step 3: Enable Key Features
Check these critical checkboxes:
- ✅ Allow Reports (analyze data).
- ✅ Allow Activities (log calls/tasks).
- ✅ Track Field History (audit changes).
- ✅ Allow in Chatter (collaborate).
- ✅ Allow Search (find records fast).
- ✅ Add Notes & Attachments (store resumes/PDFs).
Icon: ⚙️ (Settings)
Step 4: Deployment & Search Settings
- Deployment Status:
Deployed(use in production). - Search Status:
Allow Search(enable global search).
Step 5: Tab Style & Logo
- Choose an icon (e.g., 🎸 Guitar for “Positions”).
https://img.icons8.com/ios/50/guitar.png
Step 6: Add to App
- Assign to your Recruitment App (deselect others).Custom objects can live in multiple apps (e.g., Sales + Recruitment).
Step 7: Save & Verify
- Path:
Recruitment App→ See new “Positions” tab! - Test: Create a record (“Operations Manager”).
🏢 Real-Time Example: Recruitment Application
Problem: Track job openings and candidates.
Solution:
- Custom Object 1:
Position__c- Fields: Role Name, Department, Status.
- Custom Object 2:
Candidate__c- Fields: Name, Experience, Resume.
Workflow:
Emoji Flow: 🎯 Position → 👨💼 Candidate → 📎 Attachment
⚠️ Key Considerations
- Naming Limits:
- ❌ Cannot reuse names (e.g., only one
Position__c).
- ❌ Cannot reuse names (e.g., only one
- Governor Limits:
- Max 900 custom objects (depends on license).
- Deployment Status:
In-Developmentvs.Deployed(use latter for production).
❓ Interview Q&A
Q1: “How do custom objects differ from standard objects?”
Answer:
“Standard Objects (e.g., Account) are pre-built by Salesforce and immutable. Custom Objects (e.g.,
Position__c) are user-created for specific needs, fully customizable, and can be deleted.”
Q2: “Explain the ‘Record Name’ field.”
Answer:
“It’s the default identifier for records (e.g., ‘Operations Manager’ in
Position__c). You can set it as Text or Auto Number (e.g.,POS-001for unique IDs).”
Q3: “Why enable ‘Track Field History’?”
Answer:
“It audits data changes (e.g., if a job’s status moves from ‘Open’ to ‘Closed’). Critical for compliance and debugging.”
Q4: “Can one custom object appear in multiple apps?”
Answer:
“Yes! For example,
Position__ccan live in Recruitment and HR Analytics Apps. Configure during object setup.”
💡 Pro Tips
- Plural Labels Matter: Use intuitive names (e.g., “Positions” not “Positiones”).
- Attachments: Enable to store resumes/offer letters (max 25 MB/file).
- Auto Number: Use for IDs (e.g.,
CAN-100) to avoid duplicates.
✅ Conclusion
Today, you’ve built your first custom object! 🎉
- Key Takeaway: Custom objects let Salesforce adapt to YOUR business.
- Next: Fields (Day 4) – add data points like Salary or Experience!
Emoji Recap: 🧩 (Custom Object) → 🏷️ (Label) → ⚙️ (Settings) → 🎸 (Tab Style) → 🎯 (Real-Time Use Case)
Action Item: Create Position__c and Candidate__c objects in your org!
👉 Stuck? Drop questions below! 💬