[SalesForce] Lead assignment rule in a trigger

The objective is to have assignment rules fired on a Lead record creation. It seems the rule can be assigned only when using "update" DML in an "after insert" trigger. Why does another DML must be executed after insert to have lead assignment rule assigned?

//Does not work
trigger LeadTrigger on Lead (before insert) {    
    for (Lead l : Trigger.new) {        
        Database.DMLOptions dmo = new Database.DMLOptions();
        dmo.assignmentRuleHeader.useDefaultRule = true;
        so.setOptions(dmo);
    }
}


//Works: Records must be *updated* in after insert trigger in order to have the rule assigned
trigger LeadTrigger on Lead (after insert) {
    List<Lead> ls = new List<Lead>();

    for (Lead l : Trigger.new) {
        ls.add(new Lead(id = l.id));
    }

    Database.DMLOptions dmo = new Database.DMLOptions();
    dmo.assignmentRuleHeader.useDefaultRule = true;
    Database.update(ls, dmo);
}

Moreover, testing of the rule assignment fails even though the rule has been assigned to the Lead. We cannot test assignment rule outcome (ownerId=defaultQueueId for example) since the rule will change on PROD eventually.

//Test method failing for a lead *having* rule assigned:    
public static void assertDefaultAssignmentRules(SObject sobj) {
    Database.DMLOptions dmo = sobj.getOptions();

    System.assertNotEquals(null, dmo, 'DMLOption is null');
    System.assert(dmo.assignmentRuleHeader.useDefaultRule, dmo);
}

Best Answer

Lead reassignment within a trigger can be done with future methods such as the following. Your after insert / after update trigger will need to collect up a set of lead ids that qualify for reassignment and then once all other afterinsert/afterupdate operations are complete, call the future method below:

Note use of DmlOptions:

@future
public static void futureLeadReassign(Set<ID> lIdReassignSet) { 
    
    List<Lead> lUpdList = [SELECT Id FROM Lead WHERE Id IN: lIdReassignSet];
    Database.DMLOptions dmo = new Database.DMLOptions();
    dmo.assignmentRuleHeader.useDefaultRule = true;         
    for (Lead l:lUpdList) {
        // use leadAssignment rules when updating
        l.setOptions(dmo);
    }
    
    try {update(lUpdList);}
    catch (DmlException e) {/* do something here like send email to sysad with error */}
}

Related Solutions

[SalesForce] How to avoid creation of duplicate Opportunity Contact Role for every newly created Opportunity

I think it may be happening because of this section of code which initializes the conId to null and also has a break inside the if statement in the middle of the for loop. The conId will be null if not set to null anyway. I suggest you remove both the break; and leave the initialization as simply Id conId;. You may need to add a null check before adding values to your map at the end of the 1st major loop.

for(Account a: accList)
{ 
    Id conId=null;  <<== Remove the initalizion to null.
    if(a.contacts.size()>0)
    {
        //Get contact of recent LastActivityDate
        conId = a.contacts.get(0).Id;
        //Get contact where From A2Z TRUE and overwrite above contact id if found
        for(Contact c: a.contacts)
        {
            if(c.From_A2Z__c==true)
            {
                conId=c.Id;
                break;  <<== remove this break
            }
        }
    }
    // regardless, may need to add if(conId != null){
    mapOfAccIdNConId.put(a.Id,conId);
    // }
}

With that having been said, you may have other workflow in your org that's creating the OCR for you automatically and your trigger may not be needed at all. Since you've also not included the remainder of your code that might tell us what else could be contributing to your issues, there's nothing more I can tell you.

How to run the default Lead assignment rules on a Lead trigger

The assignment rule that will run is fixed at the instant the DML operation starts. In other words, by the time your trigger has started running, it is far too late to set an assignment rule. You would instead need to make a recursive update. Further, there are known limitations on the sObject.setOptions method; it would be recommended to use the Database.update(sObjects, dmlOptions) method. This also allows us to bulkify the logic.

static Boolean recursiveUpdate = false;
public static void runAssignmentRules(Lead[] records) {
  if(recursiveUpdate) {
    return;
  }
  Database.DmlOptions dmlOptions = new Database.DmlOptions();
  dmlOpts.assignmentRuleHeader.UseDefaultRule = true;
  recursiveUpdate = true;
  Database.update(records, dmlOptions);
  recursiveUpdate = false;
}

First, we check if we're already running recursively, and if so, we return early. Next, we set up the DML options we want to use and set the recursive flag to avoid infinite loops. After that, we run the DML operation. Finally, we reset the recursive flag in order to avoid disabling our trigger logic for legitimate repeat calls (partial save logic, more than 200 records in a transaction, multiple DML operations in the same transaction, etc).

Also, this logic needs to be run in an after update/after insert context. In a before insert/before update context, the record either doesn't yet have an ID, or will be locked against further DML operations.

Best Answer

Related Solutions

[SalesForce] How to avoid creation of duplicate Opportunity Contact Role for every newly created Opportunity

How to run the default Lead assignment rules on a Lead trigger

Related Topic