[SalesForce] When Merging Accounts, how may I distinguish child records of the “losing account”

When merging accounts, I want to be able to update the owner of the re-parented opportunities, and custom objects under account to the owner of the "winning" account.

My current trigger runs "after delete" and will grab all the associated opportunities for each account and associate them to the owner. This doesn't provide the distinction between the child records, the opportunities that were not re-parented should remain the same and not have their owners modified.

One thing that I was considering is creating a field that will be populated with a value "before delete" and access those in my "after delete" trigger. I thought this solution would be rather messy and was wondering if there was a cleaner way to figure out which records belonged to the losing account in a merger.

Thanks in advance!

Code:

trigger updateOwnerMerge on Account (after delete) {
//Create List of account IDs that have  been merged
List<Id> acctIDs = new List<Id>();
for (Account a : Trigger.Old) {
    //If the Record has been deleted through a merge, add winning account of merge to List
    if (a.MasterRecordId != NULL) {
        acctIDs.add(a.MasterRecordId);
    }
}
//If there are any accounts that have been merged
if(acctIDs.size() != 0) {
    //Map to associated account ID to account owner
    Map<ID, ID> accountOwner = new Map<ID, ID>();
    //Query SOQL to find all potential accounts
    List<Account> accounts = [Select ID, OwnerID from Account where ID in: acctIds];
    for (Account acc : accounts) {
        //Add account ID, Owner association to map
        accountOwner.put(acc.Id, acc.OwnerId);        
    }
    update updatedApps;
    //Find all opportunities related to account, update owner of open opportunities
    List<Opportunity> opps = [Select ID, OwnerID, AccountID, IsClosed from Opportunity where AccountID in: accounts];
    List<Opportunity> updatedOpps = new List<Opportunity>(); 
    for (Opportunity opp: opps) {
        if(!opp.IsClosed) {
            if(opp.OwnerID != accountOwner.get(opp.AccountID)) {
                opp.OwnerID = accountOwner.get(opp.AccountID);
                updatedOpps.add(opp);
            }
        }
    }
    update updatedOpps;
}

}

Best Answer

You better write a trigger on Opportunity. Check if owner is same as owner of account, if not-make it same.

trigger updateOwnerMerge on Opportunity(before update) {
//query account here to fetch account owner, replace Trigger.new below with results
for(Opportunity o: Trigger.new)({
if(o.owner!=o.Account.Owner){
o.owner=o.Account.Owner;
}
}
}

Related Solutions

[SalesForce] Account Merge – Opportunity is not updated / touched

From the Apex Developer's Guide:

Merge events do not fire their own trigger events. Instead, they fire delete and update events as follows:

Deletion of losing records A single merge operation fires a single delete event for all records that are deleted in the merge. To determine which records were deleted as a result of a merge operation use the MasterRecordId field in Trigger.old. When a record is deleted after losing a merge operation, its MasterRecordId field is set to the ID of the winning record. The MasterRecordId field is only set in after delete trigger events. If your application requires special handling for deleted records that occur as a result of a merge, you need to use the after delete trigger event.

Update of the winning record A single merge operation fires a single update event for the winning record only. Any child records that are reparented as a result of the merge operation do not fire triggers. For example, if two contacts are merged, only the delete and update contact triggers fire. No triggers for records related to the contacts, such as accounts or opportunities, fire.

The following is the order of events when a merge occurs:

The before delete trigger fires.

The system deletes the necessary records due to the merge, assigns new parent records to the child records, and sets the MasterRecordId field on the deleted records. )

The after delete trigger fires.

The system does the specific updates required for the master record. Normal update triggers apply.

Thus you could have a before delete trigger on the deletion of the losing records and figure out the children that will be affected. I suspect that you might need to have some co-ordination between the before and after delete triggers, such that the before figured out the affected children of a delete, and the after confirmed that they were being deleted as part of a merge and took appropriate action.

[SalesForce] Unit Test is Providing 0% Coverage for Apex Trigger

The trigger code is having lot of redundancy, So I modified it. before posting the modified code few lines of explanation what I changed. you collected account Ids twice and did the condition check twice where once is more enough. I am also made changes to the test class, where Task data is provided which is not required because the trigger has to create it once the necessary conditions are met. I am expecting this trigger should work for you, if there is any errors feel free to post as a comment.

trigger OpportunityAfter on Opportunity (after update){

    Set AccountIDs = new Set();

    for(Opportunity o : trigger.new){
        if(opp.StageName == 'Closed - Lost' && opp.Business_Line__c == 'Workforce' && 
            opp.Survey_Type__c != 'APulse' && trigger.oldMap.get(opp.Id).StageName != opp.StageName){

                AccountIDs.add(o.AccountId);
         }
    }

    Task[] tasksToInsert = new Task[]{};

    for (Account acc : [Select Id, Name, OwnerId from Account where Id IN :AccountIds]){
        for (Opportunity opp : trigger.new){
            if(opp.AccountId == acc.Id){
                Task tas = new Task();
                tas.WhatId=acc.Id;
                tas.OwnerId=opp.OwnerId;
                tas.Subject='Follow-up: ' + opp.name + ' - ' + acc.name;
                tas.ActivityDate=(opp.CloseDate + 180);
                tas.Description='Follow up to see how engagement initiatives are going and if Avatar can help. Refer to lost opportunity: ' + opp.name;
                tasksToInsert.add(tas);                                                         
            }
        }
    }
    if(tasksToInsert != null && !tasksToInsert.isEmpty())
    Database.insert(tasksToInsert);

}

@isTest
public class TestClass {

    static testMethod void myUnitTest() {

    //Set up user
    User u1 = [SELECT Id FROM User WHERE Email='abc@sampleemail.com'];
    test.startTest();  
    //Run As U1
    System.RunAs(u1){

    System.debug('Testing trigger... (single record validation)');

    //NEW Account record
    Account acc = new account();
    acc.Name = 'Test Account';
    acc.Industry = 'Healthcare';

    insert acc;

    //NEW Opportunity record
    Opportunity opp = new Opportunity();
    opp.Name = 'Test Opportunity'; 
    opp.CloseDate = System.today();
    opp.StageName = 'S1 - Investigative';
    opp.Type = 'Repeat Business - Wrkforce HC';
    opp.AccountId = acc.Id;
    opp.Survey_Type__c = 'Product Name';

    insert opp;

    opp.StageName = 'Closed - Lost';
    opp.Reason_Won_Lost__c = 'Relationship';
    opp.Business_Line__c = 'Workforce'  //added this line to meet the if condition while collecting the set of id in the trigger.

    update opp;
   test.stopTest();
    // Here I am expecting the task has been inserted and doing a query for it         and check it in the assert statement.
   Task  testTask=[Select Id, WhatId from Task where WhatId=:acc.Id];
    //Validate single insert
    System.assertEquals(acc.Id, testTask.WhatId);

    }
    }
}

Best Answer

Related Solutions

[SalesForce] Account Merge – Opportunity is not updated / touched

[SalesForce] Unit Test is Providing 0% Coverage for Apex Trigger

Related Topic