MENU
UC is building a salesforce application to track contacts and their respective conferences that they have attended with the following requirements:
1. Contacts will be stored in the standard contact object.
2. Conferences will be stored in a custom conference_ c object.
3. Each contact may attend multiple conferences and each conference may be related to multiple contacts.
How should a data architect model the relationship between the contact and conference objects?
Implementing a Contact Conference junction object with master detail relationship to both contact and conference_c is the correct way to model the relationship between the contact and conference objects, as it allows a many-to-many relationship between them. This means that each contact can attend multiple conferences, and each conference can be related to multiple contacts. Creating a master detail relationship field on either the contact or the conference object would create a one-to-many relationship, which does not meet the requirements. Creating a lookup relationship field on contact object would also create a one-to-many relationship, and would not enforce referential integrity.