In Salesforce, data is stored in objects like Account, Contact, Opportunity, and custom objects. But in real business scenarios, data is never isolated. Different objects need to be connected with each other.
For example:
- A Customer (Account) can have many Contacts
- An Order can have multiple Order Items
- A Student can enroll in many Courses
To manage these connections, Salesforce provides object relationships.
Among all relationship types, the two most important ones are:
- Master-Detail Relationship
- Lookup Relationship
In this article, we will understand:
- What is a Master-Detail Relationship
- What is Lookup Relationship
- Key differences between them
- Real-time examples
- When to use which relationship
- Common mistakes and best practices
By the end, you will clearly understand how to design Salesforce data models correctly.
What is a Relationship in Salesforce?
A relationship in Salesforce defines how two objects are connected. It tells Salesforce how one record relates to another.
For example:
- Contact → Account
- Case → Contact
- Opportunity → Account
Relationships help in:
- Data organization
- Reporting
- Automation
- Data integrity
Salesforce mainly uses relationships to create parent-child connections between records
Salesforce object relationships connect different data entities to create a linked information network. These connections allow users to access related data across objects seamlessly.
Defining Custom Objects in Salesforce
Custom objects in Salesforce let businesses store unique data types. Users can create these objects to fit their specific needs. Custom objects work like standard objects but are tailored to a company’s processes.
To make a custom object:
- Go to Setup
- Click “Object Manager“
- Select “Create” then “Custom Object.“
- Name the object and set its options
Custom objects, such as text, numbers, and dates, can hold various field types. They form the basis for building relationships between different data sets in Salesforce.
Exploring Relationship Fields in Salesforce
Relationship fields link objects in Salesforce. They create connections that let users view related data across records. These fields come in two main types: lookup and master-detail.
Lookup fields create a simple link between objects. They’re flexible and don’t require the linked records to exist. Master-detail fields create a stronger bond. The “detail” record can’t exist without its “master.”
When setting up relationship fields, users choose the objects to connect and set field properties. This process shapes how data flows between different parts of the Salesforce system.
Types of Relationships in Salesforce
Salesforce offers several relationship types to suit different data structures.
- One-to-Many: One record links to multiple related records.
- Many-to-Many: Records on both sides can link to multiple records on the other side.
- One-to-One: Each record links to only one other record.
Master-detail relationships create a tight coupling in which the detail record depends on the master. Lookup relationships are more flexible, allowing independent records.
Here’s a quick comparison:
| Feature | Lookup | Master-Detail |
|---|---|---|
| Dependency | Low | High |
| Deletion | Independent | Cascade |
| Sharing | Separate | Inherited |
Master-Detail vs Lookup Relationships in Salesforce
Choosing the right relationship type is key to building an effective Salesforce data model.
What is Lookup Relationship in Salesforce?
A Lookup Relationship is a loose connection between two objects.
Lookup relationships in Salesforce provide a flexible way to connect objects. They allow for loose coupling between records while enabling customizable visibility and sharing.
Key Features of Lookup Relationship
- Parent record is not mandatory
- A child record can exist without a parent
- No automatic deletion (no cascade delete)
- Each object has separate security
- No roll-up summary fields (by default)
Lookup relationships link two objects in Salesforce. They create a field on one object that references another object. This link is optional, so a record can exist without filling the lookup field.
Lookup relationships don’t enforce strict rules between objects. A child record can exist even if its parent is deleted, allowing greater flexibility in managing data.
These relationships support many-to-many connections. One record can link to multiple others through lookups. This flexibility is helpful for complex data models.
Example of Lookup Relationship
Let’s say:
- You have a Project object
- You have an Employee object
You can create a lookup: Employee → Project
But:
- An employee can exist without a project
- The project can be deleted without deleting the employee
Flexibility and Use Cases
Lookup relationships offer great versatility in Salesforce. They connect related but independent objects, such as linking a case to a product or an opportunity to a campaign.
Common use cases include:
- Connecting employees to departments
- Linking tasks to projects
- Associating contacts with accounts
Lookups allow for optional connections. This is helpful when not all records need to be linked. It gives users the choice to make connections as required.
Visibility and Sharing Settings
Lookup relationships respect object-level security settings. Each object maintains its sharing rules and visibility settings, so access to a parent record doesn’t automatically grant access to linked child records.
Users can see lookup fields if they have read access to both objects. However, viewing the lookup does not mean they can access the linked record’s details.
Administrators can control which related lists appear on page layouts. This helps manage what users see when viewing records with lookup relationships.
What is a Master-Detail Relationship?
A Master-Detail Relationship is a strong parent-child relationship. A child record cannot exist without a parent.
Master-detail relationships in Salesforce create a strong link between objects. They offer unique features that help manage data and access.
Key Features of Master-Detail Relationship
- Parent record is mandatory
- The child’s record depends on the parent
- Cascade delete (auto deletion)
- Inherits security from parent
- Supports roll-up summary fields
A master-detail relationship connects two objects in Salesforce. The master object controls key aspects of the detail object, making this link stronger than a lookup relationship.
In this setup, one object is the master (or parent), and the other is the detail (or child). The detail object can’t exist without its master, and this tight bond affects how data is handled and viewed.
Users pick the master object when making a new detail record. This ensures each detail has a master.
Example of Master-Detail Relationship
Let’s say:
- Order (Master)
- Order Item (Detail)
If the Order is deleted: All Order Items are automatically deleted. This ensures data consistency
Data Integrity and Cascade Delete
Master-detail relationships keep data clean and connected. When a master record is deleted, all its detail records are removed. This is called cascade delete.
Cascade delete helps maintain data integrity. It prevents orphaned records that could cause errors or confusion.
For example, if a customer (master) is deleted, all their orders (details) are removed. This keeps the database tidy and accurate.
Salesforce doesn’t allow users to change this behavior. It’s a key feature of master-detail relationships.
Roll-Up Summary Fields and Object Ownership
Roll-up summary fields are particular fields on master objects. They can show totals, counts, or other calculations from detailed records.
These fields update automatically when detailed records change. This gives quick insights without running reports.
For instance, a master account could show the total value of all related orders.
In master-detail relationships, the detail object inherits its sharing settings from the master. This means access to detailed records is based on access to the master.
The master object also owns the detail records. This affects reporting and the organization of data in Salesforce.
Master-Detail vs Lookup Relationship in Salesforce
| Feature | Lookup Relationship | Master-Detail Relationship |
|---|---|---|
| Relationship Type | Loose | Strong |
| Parent Required | No | Yes |
| Child Dependency | Independent | Dependent |
| Cascade Delete | No | Yes |
| Security | Separate | Inherited |
| Roll-Up Summary | Not Available | Available |
| Record Ownership | Separate | Controlled by Master |
| Flexibility | High | Low |
When to Use Lookup vs Master-Detail Relationship in Salesforce
Use Lookup Relationship When:
- Records should exist independently
- Parent is optional
- No need for roll-up summary
- Flexible data model required
Use Master-Detail Relationship When:
- A child must always have a parent
- Need roll-up summary fields
- Need automatic deletion
- Want strict data control
Security & Sharing Difference
Lookup:
- Each object has its own security
- Access is independent
Master-Detail:
- A child inherits their parents’ security
- If the user cannot access the parent → cannot access the child
This is important for admin and security design.
Frequently Asked Questions
Salesforce offers two key relationship types: lookup and master detail. These options have distinct features and uses. Let’s explore common questions about them.
What is the difference between lookup and master-detail relationships in Salesforce?
Lookup relationships are more flexible. They allow objects to exist independently. Master-detail relationships create a strong link between objects. The detail object depends on the master object’s existence.
Lookup relationships don’t affect record ownership or sharing. Master-detail relationships do. The detail record inherits security settings from its master.
How to create a master-detail relationship in Salesforce?
To create a master-detail relationship, go to the Object Manager, select the detail object, click “Fields & Relationships,” and then “New,” choose “Master-Detail Relationship,” and pick the master object.
Set the field label and name. If needed, choose roll-up summary options. Set field-level security and page layout settings. Save your changes.
Can a master-detail relationship be converted to a lookup relationship in Salesforce?
Yes, you can change a master-detail relationship to a lookup. In the Object Manager, open the relationship field, click “Edit,” and change the relationship type to “Lookup.”
This change can affect data access and roll-up summaries. Make sure to review and adjust sharing rules after conversion.
What are the limitations on the number of master-detail relationships in Salesforce?
Up to two master-detail relationships can exist between objects, and custom objects can be on the detail side of up to two master-detail relationships.
Standard objects can’t appear on the detail side of a master-detail relationship with custom objects. The number of lookup relationships is unlimited.
When should a master-detail relationship be used instead of a lookup relationship in Salesforce?
Use master detail when objects are closely linked. It’s good for parent-child relationships where the child can’t exist alone. Examples include orders and order items or accounts and contacts.
Master detail is useful for rollup summaries and cascading deletions. It’s ideal when you want automatic sharing and ownership inheritance.
What key characteristics differentiate a lookup relationship from a master-detail relationship in Salesforce?
Lookup relationships are more independent. Records can exist independently and have separate owners. They don’t allow roll-up summaries or affect sharing rules.
Master detail creates a strong bond. Detailed records can’t exist without a master. They share the master’s access settings. Master-detail enables rollup summaries and cascading deletions.
Conclusion
Salesforce offers two main types of relationships: lookup and master-detail. Each has unique features that suit different needs.
Lookup relationships are flexible. They allow for optional connections between objects. This works well for loose associations.
Master-detail relationships strengthen bonds and tie objects closely together. Detailed records depend on their master records for several functions.
The choice between these two depends on specific requirements. Lookup works best for independent records that may or may not be linked. Master-detail relationships work well when child records rely heavily on parent records.
You may like to read:
- Create Self Relationship in Salesforce
- Create Lookup Relationship in Salesforce
- Delete a Master-Detail Relationship in Salesforce
- Convert Master-Details Relationship into Lookup in Salesforce
I am Bijay Kumar, the founder of SalesforceFAQs.com. Having over 10 years of experience working in salesforce technologies for clients across the world (Canada, Australia, United States, United Kingdom, New Zealand, etc.). I am a certified salesforce administrator and expert with experience in developing salesforce applications and projects. My goal is to make it easy for people to learn and use salesforce technologies by providing simple and easy-to-understand solutions. Check out the complete profile on About us.
