You need to sign in to do that
Don't have an account?

Master-Detail and Lookup
Hi All,
Can anyone please explain the below
1. What is Master-Detail and Lookup relations / Major difference b/w them ?
2. What is the significance/use of Master-Detail and Lookup ?
3. When to use Master-Detail and Lookup ?
Thanks a ton in advance !
Regards,
SK
Sure man,
Hope this gives you a little insight, although there are a lot of such examples with different functionalities, but i'm sure you'll know it as you start working with it.
Thanks
[do mark it as a solution or give kudos if you think i helped you any bit. ;) ]
All Answers
Hey SK_R
This is a pretty famous question here in developer forum.
Still i would give you a little clue from my end.
Lookup relationship : Loosely coupled relationship
Master-Detail : Tightly coupled relationship.
Apart from this I'll give a link to another discussion on the same topic, the solution is really nice, please have a look :
http://boards.developerforce.com/t5/General-Development/Difference-between-Lookup-Relationship-and-Master-Detail/td-p/209011
The line between the two is becoming more blurred, so perhaps it is becoming more difficult to distinguish.
For instance, it used to be that Master-Detail fields were required, lookups weren't.
Now, we can make lookups required (except for where certain parent objects are standard objects, User and Product, for instance).
Master-Details always cascade delete.
Lookup relationships can be made to either not cascade delete, block delete of the parent to prevent orphan children, or cascade delete (although cascading creates some permissions anomalies, so you must contact support to enable this feature).
When choosing which to use, the feature the feature that gets overlooked a lot by people who are new to the platform is the inheriting of permissions access from parent to child in the Master-Detail relationship. The reason being is this: if I have a use case where I must grant access to parent data, but must not automatically grant access to the children, I can't use Master-Detail.
Another item that is important is reporting. And this, I confess, I don't understand very well, but the type of relationship you use changes the way that data is available across relationships, in reports.
Start with the resource that Manish shared, get building, and then, if you come to a particular use case and aren't sure if you are designing correctly, come back and ask again.
Hi Manish,
Thank you for your reply.
Apart from these differences , what is the use / purpose of these relationships ?. When to choose Master-Detail, when to choose look up fileds ?.
Can you please give a real time scenario ?
Thanks in advance !
SK
Sure man,
Hope this gives you a little insight, although there are a lot of such examples with different functionalities, but i'm sure you'll know it as you start working with it.
Thanks
[do mark it as a solution or give kudos if you think i helped you any bit. ;) ]
Thank you very much for explaination.
Regards,
SK.