Matchmaker KB 1008: Fixing custom Account lookup data after upgrading to version 1.11.5.

Issue

An issue discovered in version 1.11.4 and earlier affects customers using Matchmaker with their own custom lookup field. This issue sometimes caused the lookup field not to populate. Specifically, a custom lookup field would not be populated when a lead had more than one potential account matche and the configured Match Prioritization Rules narrowed the matches down to one account. In this scenario, Matchmaker's Matched Account field was set, but the custom lookup field was not.

Impact

This bug's effect on customer data is as follows:

• The customer's custom lookup field is sometimes not set. This prevents any custom processes, workflows, or code using this lookup field not to work as expected.
• If the customer is also using Matchmaker for lead assignment and conversion, these processes will not run for the affected leads.

Solution

After upgrading to 1.11.5, the following code can be run in the Developer Console to set the custom lookup field on leads where it is missing but Matchmaker's Matched Account field is populated.

If the customer is also using Matchmaker for lead assignment and conversion, these processes will be triggered when the field is populated.

Notes:

• You may need to replace "LIMIT 10000" with a lower number if the code fails to execute successfully.
• Replace "Custom_Lookup__c" with the API name of your custom account lookup field.

List<Lead> leadsToUpdate = [SELECT Custom_Lookup__c, FCMM__LAM_MatchedAccount__c FROM Lead WHERE IsConverted=false AND FCMM__LAM_MatchedAccount__c != null AND Custom_Lookup__c = null LIMIT 10000];
for (Lead lead : leadsToUpdate) {
lead.Custom_Lookup__c = lead.FCMM__LAM_MatchedAccount__c;
}
update leadsToUpdate;