One-to-Many Relationship
A One-to-Many Relationship in Salesforce means a single parent record can be associated with multiple child records.
Definition
A One-to-Many Relationship in Salesforce means a single parent record can be associated with multiple child records. This is the most common relationship type and is created using either a Master-Detail field (tightly coupled, where child records inherit sharing/security and are deleted if the parent is deleted) or a Lookup field (loosely coupled, where child records can exist independently of the parent).
In plain English
“A One-to-Many Relationship in Salesforce means one parent record can have many child records. Like one Account can have many Contacts. You implement it with either Master-Detail (tightly coupled) or Lookup (loosely coupled) relationships, depending on whether the parent owns the children.”
Worked example
TechCorp is an enterprise customer of Northwind Trading. The single TechCorp Account in Salesforce has 12 active Opportunities - a renewal in Q3, a major upsell in Q4, three expansion deals across different business units, and several pilot programs. This is a One-to-Many Relationship: one parent (the Account) connected to many children (the Opportunities), where each Opportunity has a lookup pointing back to TechCorp. Reports rolled up at the Account level show total pipeline value across all 12 Opportunities; account team members see the full deal portfolio rather than tracking each Opportunity in isolation.
Why One-to-Many Relationship matters
A One-to-Many Relationship in Salesforce means a single parent record can be associated with multiple child records. This is the most common relationship type and is created using either a Master-Detail field (tightly coupled, where child records inherit sharing/security and are deleted if the parent is deleted) or a Lookup field (loosely coupled, where child records can exist independently of the parent). Common examples include Account-to-Contact, Account-to-Opportunity, and many custom parent-child structures.
Choosing between Master-Detail and Lookup matters significantly for the relationship's behavior. Master-Detail creates ownership: children belong to the parent, inherit its sharing, and are deleted with it. This is appropriate when children only make sense in the context of their parent (like line items belonging to an order). Lookup creates association: children can exist without a parent and have their own ownership. This fits when records are related but independent (like a Contact that might or might not have an Account). Mature data models think carefully about which relationship type fits each parent-child pattern.
How organizations use One-to-Many Relationship
Uses Master-Detail for line items belonging to orders (where line items only make sense with their order) and Lookup for most other relationships.
Documents the rationale for each Master-Detail vs Lookup choice in their data model so future admins understand the reasoning.
Treats relationship choice as a foundational data model decision with implications for sharing, deletion, and ownership.
Trust & references
Straight from the source - Salesforce's reference material on One-to-Many Relationship.
- Object Relationships OverviewSalesforce Help
Test your knowledge
Q1. What is a One-to-Many Relationship?
Q2. How is it implemented?
Q3. When use Master-Detail over Lookup?
Discussion
Loading discussion…