Relationships in Salesforce
Object Relationships in Salesforce
- Master-Detail
- Lookup
- Many-to-Many
- When a record of the master object is deleted, its related detail records are also deleted.
- The Owner field on the detail object is not available and is automatically set to the owner of its associated master record. Custom objects on the detail side of a master-detail relationship cannot have sharing rules, manual sharing, or queues, as these require the Owner field.
- The detail record inherits the sharing and security settings of its master record.
- The master-detail relationship field is required on the page layout of the detail record.
- By default, records can’t be reparented in master-detail relationships. Administrators can, however, allow child records in master-detail relationships on custom objects to be reparented to different parent records by selecting the Allow reparenting option in the master-detail relationship definition.
Lookup Relationship (1:n)
This type of relationship links two
objects together, but has no effect on deletion or security. Unlike
master-detail fields, lookup fields are not automatically required. When
you define a lookup relationship, data from one object can appear as a
custom related list on page layouts for the other object. See
the Salesforce online help for details.
- Child row not automatically deleted when a parent row is deleted
- No inherited sharing.
- 25 lookup relation relationships allowed per object.
- Lookup field on child not necessarily required.
You can use master-detail relationships to model many-to-many relationships between any two objects. A many-to-many relationship allows each record of one object to be linked to multiple records from another object and vice versa.
To create a many-to-many relationship, simply create a custom junction object with two master-detail relationship fields, each linking to the objects you want to relate.
No comments:
Post a Comment