Definition
Relationship is a connection between two Salesforce objects that associates records from one object with records from another. This link enables users to navigate between related data, build cross-object reports, and maintain referential integrity across the data model.
Real-World Example
When a sales rep at Pinnacle Corp needs to streamline operations, they turn to Relationship to manage and organize customer data more effectively. They configure Relationship to ensure the sales and service teams have a unified view of every customer interaction, from initial contact through ongoing support. This setup reduces duplicate data entry and improves cross-team collaboration.
Why Relationship Matters
A Relationship in Salesforce is a connection between two objects that links records from one object to records in another, enabling cross-object navigation, reporting, and data integrity. Salesforce supports several relationship types: Lookup (flexible, child can exist without parent), Master-Detail (tight coupling with cascade delete and sharing inheritance), Many-to-Many (through junction objects), and Hierarchical (self-relationship on User). These relationships are the structural foundation of the data model, determining how information flows between objects and what queries, reports, and automations are possible across the platform.
As a Salesforce implementation matures, the choice of relationship type has far-reaching implications. A Lookup relationship allows reparenting and independent record existence, while a Master-Detail enforces referential integrity and enables roll-up summaries. Choosing the wrong type early on can require costly migrations later. For example, converting a Lookup to Master-Detail requires that all child records already have a parent value populated, which can be a significant data cleanup effort. Organizations should plan their relationships during the initial design phase, considering not just current needs but future reporting requirements, security model implications, and automation dependencies.
How Organizations Use Relationship
- Nexus Consulting — Nexus needed to track which Consultants worked on which Projects, with each Consultant working on multiple Projects and each Project having multiple Consultants. They created a junction object called Project Assignment with Master-Detail relationships to both Consultant and Project, enabling many-to-many reporting and roll-up summaries for total hours per project and total projects per consultant.
- TideWater Marine — TideWater used a Hierarchical relationship on the Account object to represent their parent-subsidiary corporate structure. The global headquarters Account was the parent of 8 regional subsidiary Accounts, which each had their own child Accounts for local branches. This hierarchy enabled roll-up reporting that showed consolidated revenue from the corporate level down to individual branches.
- CircuitPath Electronics — CircuitPath initially created a Lookup relationship between Order and Customer, allowing orders to exist without a customer association. When they later needed roll-up summaries showing total order value per customer, they had to convert to Master-Detail, which required a data cleanup project to associate 3,400 orphaned orders with their correct customer records before the conversion could proceed.