Master-detail relationship is like parent-child relationship where, master represents a parent and detail represents a child in which master object controls some behaviors of the detail object. Like whenever a Master object record is deleted then the detail object related to it also gets deleted.
Get a good investment from data through one of the salesforce managed service providers. Micropyramid's salesforce managed services helps in testing your custom reports after converting a lookup field into a Master-detail relationship, ensuring them about their usability. Our managed service team will help you in creating and managing a Master-detail relationship before its custom object comprises data.
Master-detail relationship can be defined between custom objects or between a standard object and a custom object. The detail object automatically gets the security and sharing settings given to the master object.
A child of one master detail relationship can't become a parent of another object. To relate an object to another object, no records should exist in the child object.
Rollup summary fields can only be created on Master records, which are used to calculate the sum, avg, min etc. of child records.
How to create a Master-detail relationship:
We can't create a Master-detail relationship on existing records. To do that, we have to create a lookup relationship for that record and then convert it into master detail.
To convert a lookup relationship to a master detail the existing record should consist of valid lookup field values.
You can build many to many relationships using two master detail relationships in an object, and it is called as Junction object.
Standard objects can't be on a detail side of a master detail relationship. Access to detail is determined by the access given for master.
Limitations: