[SalesForce] Creating Opportunity and Opportunity Contact Role from Contact in LEX

In Salesforce Classic, you can create a new opportunity using a URL like the below:

/006/e?ent=Opportunity&conid={!Contact.Id}

This works great, creates the opportunity, and creates an Opportunity Contact Role using the contact id passed in.

In our org we override the "New" opportunity button in order to do some validation before we allow users to create an opportunity, and use the url parameter so that the standard screen will also create the opp contact role.

In LEX, we've converted that validation into a Lightning Action where we pass the user on to the standard opportunity Create Record. All works great, but the Opp Contact Role is not created automatically.

Is there an equivalent to the url hack used in Classic, in LEX?

Best Answer

I don't believe there's any equivalent to the Classic URL hack. This behavior is something you can automate, though, without writing any code.

Add a new lookup on Opportunity to Contact; call it Primary_Contact__c, for example. Make sure, in your Quick Action on the Contact object, that that field is selected as the "Relationship Name". (Note that if there's only one relationship field between Contact and Opportunity, you won't get to choose - that field will be selected automatically).

Now, build a new Process. Set it to run on Opportunity creation only, with a single criteria node that looks for Primary_Contact__c to not be blank.

Add an action to the criteria node to create a record, and configure it to create an Opportunity Contact Role using the Opportunity Id, the value of the Primary_Contact__c field, and whatever Role your organization prefers.

Then your Quick Action should exhibit that same behavior you expect.

Related Solutions

[SalesForce] Apex Trigger to create Opportunity Contact Role based on Contact Lookup field

Here's some modifications to your trigger that should point you in the right direction. Basically you want to use maps to do what you attempting. Your code was a bit unclear around your delete method. You don't want to do that inside your for loop one record at a time. Collect them all and do it all in a single operation.

If you want to do error handling, adjust the code to get DML save results and use your maps to equate them to the proper opportunity. Be sure to do the Delete operation FIRST since you don't want to have two primary OCR's on the same Opp record!

map<Id,Id>OpOldOcR = new map<Id,Id>();
map<Id,Id>OpNewOcR = new map<Id,Id>();

if(Trigger.isUpdate) {

  for(Opportunity opp : Trigger.new) {
      if(opp.Primary_Contact__c != null && Trigger.oldMap.get(opp.Id).Primary_Contact__c == null) {
            //Creating new Contact Role
          OpNewOcR.put(opp.Id,opp.Primary_Contact__c);
      }
        else if(opp.Primary_Contact__c != null && Trigger.oldMap.get(opp.Id).Primary_Contact__c != null) {
            //Create New Contact Role make new CR Primary over the old CR
            OpNewOcR.put(opp.Id,opp.Primary_Contact__c);
            OpOldOcR.put(opp.Id,Trigger.oldMap.get(opp.Id).Primary_Contact__c)

        }
      else if(opp.Primary_Contact__c == null && Trigger.oldMap.get(opp.Id).Primary_Contact__c != null) {
            OpOldOcR.put(opp.Id,Trigger.oldMap.get(opp.Id).Primary_Contact__c)
      }
  }

for(Id oId:OpNewOcR.keyset())
{
      newContactRoleList.add(new OpportunityContactRole(ContactId=OpNewOcR.get(oId),OpportunityId=oId,Role='Decision Maker',IsPrimary=true));
}

CtctIds.addALL(OpOldOcR.values());
list<OpportunityContactRole>toDelete = [SELECT Id, ContactId FROM OpportunityContactRole WHERE ContactId IN : CtctIds];

}

if(!toDelete.isEmpty()) delete toDelete;

if(!newContactRoleList.isEmpty()) insert newContactRoleList; 

}

[SalesForce] Apex Trigger on Opportunity Contact Role to assign primary to first contact on list

It seems that the code snippet you provieded is correct. I just copy-pasted it to my dev org and it works perfectly - the first contact is populated as primary. It's either I do your business process incorrectly or the problem isn't in that trigger. I would suggest you to test this trigger on a clean dev org and check if the first contact is not populated as primary. If so, write several debug logs to understand better code execution. If in dev org this trigger will work perfectly - you need to dig deeper into debug logs and understand what else affects Contact Roles

Best Answer

Related Solutions

[SalesForce] Apex Trigger to create Opportunity Contact Role based on Contact Lookup field

[SalesForce] Apex Trigger on Opportunity Contact Role to assign primary to first contact on list

Related Topic