[SalesForce] Junction object scenario

I have created a junction object with name JO and have 2 other objects candidate and position, have master detail relation ship form both object to junction object. My scenario is that 1 candidate related to many position and 1 position related to many candidate. That's is why I created the junction object. I have created a record in junction object and created 3 records in candidate with junction object record same as in position I created 3 records with junction object record. Now when I go to the junction object I can see all the position and candidate records related to the junction object records, that is 3 position records and 3 candidate records. But still not able to understand how 1 candidate related to many positions and 1 position related to many candidates. Can any one here guide me what I am doing wrong or any thing else I need to do over this situation.

Best Answer

Look at the following image I found on search engine: enter image description here

Here a team member is related to project. So there can be two scenarios:

A team member can be related to multiple project
A project can have multiple team members

To achieve this we create a object which will have reference to team member and project to establish relationship. Let's say the object name is: Project Team Member

So, for the scenario 1 you can create multiple "Project Team member" records which will have different team member in each record but same project reference. This way a team member can be related to multiple projects

For scenario 2, you can create "Project Team member" record which will have different Project reference but same team member reference.

This way multiple team members can be related to single project as well as with multiple projects and vice-versa. The best way to understand is do it practically you will understand how it is many-to-many relationship.

Related Solutions

[SalesForce] Junction object in Salesforce

I disagree with the "common knowledge" on this issue. I have run into use-cases where using a Lookup relationship instead is appropriate. The junction object is a more flexible concept than people give it credit for. I agree that the following are preferable:

Junction should only relate to two objects
Junction should never be orphan

However, these requirements are not terribly difficult to satisfy without the use of Master-Detail relationships. For example a Validation Rule can count all the lookups and make sure you have exactly two.

A Concrete Example

Let's say you want to mimic polymorphism in your junction. Consider, for example, if I have one object that I want to relate to five others via many-to-many relationship. Do I create five separate true junctions or one junction-like object? There are valid arguments for each side, but to flat out reject the mock polymorphism because it uses Lookup instead of Master-Detail may not be an option in all orgs (sometimes you are limited to ten custom objects).

[SalesForce] How to update contact object from related junction object

One of the things I like to do is add formula fields to my Junction objects to simplify things. So the first step would be to make a field on Sponsorship__c; I'll call it: Sponsored_Child_Name__c.

Formula: Sponsored_Child__c.First_Name__c

Another very important thing to keep in mind is bulkification:

Pseudo Code

trigger triggerName on Sponsorship__c (events) {
if (event) { // trigger.isUpdate, trigger.isBefore, etc
Map<Id, Sponsorship__c> contactToSponsorship = new Map<Id, Sponsorship__c>();
Lisit<Contact> contactsToUpdate = new List<Contact>();

for (Sponsorship__c s : trigger.new) {
contactToSponsorship.put(s.contact__c, s);
}

for (Contact c : [SELECT Child_Names__c FROM Contact WHERE Id IN :contactToSponsorship.keySet()]) {
c.Child_Names__c += contactToSponsorship.get(c.Id).Sponsored_Child_Name__c;
contactsToUpdate.add(c);
}

update contactsToUpdate;
}

That should get you close.

Best Answer

Related Solutions

[SalesForce] Junction object in Salesforce

[SalesForce] How to update contact object from related junction object

Related Topic