#Duplicates3 discussing

Hi Trailblazer Community, 

I am working on a Salesforce Flow solution for Account merges and would appreciate guidance. 

When two duplicate Accounts are merged, the surviving Account should automatically recalculate two custom count fields updated by a flow 

Current design: 

I built this as a two-part flow process. 

Flow 1: 

Record-Triggered Flow on Account 

Trigger: A record is deleted 

Optimize for: Before the record is deleted 

Entry condition: 

MasterRecordId Is Null False 

Purpose: 

When an Account is deleted because of a merge, the flow creates a Platform Event record. 

Flow 2: 

Platform Event-Triggered Flow  

Purpose: 

When the Platform Event is received, it uses Surviving_Account_Id__c to: 

1. Get all related Case Records  

2. Count those records. 

3. Get active x Records where: 

4. Count active records. 

5. Get the surviving Account. 

6. Update Account if necessary 

What I confirmed: 

The Platform Event is deployed and has Publish Behavior = Publish After Commit. 

The Platform Event-triggered flow is subscribed and running. 

When I manually publish the Platform Event through Developer Console, Flow 2 works correctly and updates the Account counts. 

After this manual publish, the Account count fields update correctly. 

Issue: 

When I perform an actual Account merge, the surviving Account counts do not always update automatically. 

I confirmed that the losing Account has: 

IsDeleted = true 

MasterRecordId = surviving Account Id 

So Salesforce is populating MasterRecordId correctly. 

Question: 

Is there anything about Account merge delete behavior, before-delete flows, or Platform Event publishing from a record-triggered delete flow that would prevent the Platform Event from being published or processed as expected? 

Also, is there a better declarative pattern to recalculate rollup-style count fields on a surviving Account after an Account merge?

Any guidance would be appreciated. 

I created and activatted the following new account "matching rule" based on the account's shipping address, not the billing address:

(Account: Name > FUZZY: COMPANY NAME MatchBlank = FALSE) AND 

(Account: ShippingStreet > FUZZY: STREET MatchBlank = FALSE) AND 

(Account: ShippingState > EXACT MatchBlank = FALSE)

However, when I updated the Account Duplicate Rule to this new Matching Rule, accounts that match this rule are not triggering the "duplicate warning"

What am I missing? Any help or insight would be greatly appreciaited!

#Sales Cloud  #Salesforce Developer  #Data Management  #Automation #Duplicates #Duplicate Rules #Matching Rules

Hello Team,

We are on reverse sync (no lead objects but only contact records in SF).

We have 2 duplicate scenarios;

1. When duplicate records are merged in Salesforce (same first name, last name, email address), they are merged in Pardot too. This is all good.

2. We have contact records with different first names and last names but they all share the same email address. This is a peer-to-peer fundraising scenario where Person A collects donations from 3 others (B, C, D) and updates all the donations under Person A's email address. What we currently do in Salesforce is, remove the email addresses from Person B, Person C, and Person D contact records and simply add them as a relationship type to Person A (Who has the original email address). This works well in Salesforce. However, in Pardot, the Person B, Person C, and Person D records still exist as orphan prospects (even though the opportunity is dissociated from their records).

What we like to happen in this scenario is when an email is removed from a SF contact, the prospect record gets deleted in Pardot too.

Please advise if there are any settings I can activate to achieve this outcome.

Thanks

#Pardot B2b Marketing Automation, #Duplicates

Hi All, 

I am having some issues with my duplicate and matching rules.

I believe the matching rule that I am building to be quite basic it is performing a fuzzy match on the account name and an exact match on the phone number or email address. Both phone and email are also selected to match if blank.

(Account: NameFUZZY: COMPANY NAMEMatchBlank = FALSE) AND ((Account: PhoneEXACTMatchBlank = TRUE) OR (Account: Company_EmailEXACTMatchBlank = TRUE))

I have one example in my org where there are 4 accounts, all owned by the same account owner, all have roughly the same company name, give or take Ltd, Limited, Plc etc, 2 have a matching phone number and 2 have blank phone numbers and all 4 have blank email address.

When I am logged in as the account owner, the lighnting component tells me that there are potential duplicates but only shows the accounts with the phone numbers.

I can only assume this is user error on my part but I thought that selecting match on blanks would include these other accounts when offering potential duplicates.

Am i missing a selection somewhere or not executing this correctly?

any advice would be greatly appreciated.

many thanks

Laura

#Duplicates #Matching Rules #Duplicate Rules #Sales Cloud

I've written an Apex class with methods that parse data out of a CSV file, create account and contact lists with custom fields used as external IDs, and upsert that data using the custom fields as the comparison for duplicates. However, Apex thinks the data in the contact list contains duplicates. I have confirmed in the file itself and via debug code (comparing against a set) that it does not, and I can see when I write debug code to only add the contact to the list if it is not already in the list that Apex thinks every record is a duplicate. 

I've written code to ensure and confirm that the list is empty before I start adding to it, I've edited the match rules so they only match on the external ID, and I've uninstalled Dupe Eliminator and Duplicate Check (installed by my predecessor) to be sure they aren't creating restrictions I can't access. Also, I've tried to check Apex triggers, but they are managed and can't be viewed/edited. We do have quite a few other packages/apps installed. Could these be the issue? Could it be a scope of the variable issue? Does anyone have any suggestions on what else might be the issue? 

I am including my code below with the caveat that it is pretty messy right now with all my debug code, comments, and variables for other methods in place. Below that code is a screenshot of the debug log starting at the beginning where you can see the first test for the contact existing in the list results in TRUE, before any other contact has been added to the list, and that there is no debug output for the code outputting

 any contacts already in the list before I start adding to it. Finally, I am also including a screenshot of our installed packages.

public class mkfa_ImportLegacyData {
    //Create an affiliation, contact, and account list for those being manipulated by methods.
    public static List<npe5__Affiliation__c> affiliationList = new List<npe5__Affiliation__c>();
    public static List<Contact> contactList = new List<Contact>();
    public static List<Account> accountList = new List<Account>();
    //Create string lists for holding all data & 1 row from document
    public static List<String> dataRecs = new List<String>();
    public static List<String> fieldValues = new List<String>();
    public static List<List<String>> parsedData = new List<List<String>>();
    public static Boolean proceedFlag = true;
    //Create a contact,account, affiliation, and IDs
    public static Contact tempContact = new Contact();
    public static VOID parseFileRecs(string docName){
        //Get the file
        final ContentVersion doc = [SELECT VersionData FROM ContentVersion WHERE Title = :docName AND IsLatest = true];
        //******CSV file must be in UTF-8 format******
        String bodyString = doc.VersionData.toString();
		//Split the content into records by new line character
        dataRecs = bodyString.split('\n');    
        //Debug code
        //system.debug('Body of the document to import:'+bodyString);  
        //Iterate through the records in the file to create a list of recs, sans the header, each of which is a list of fields
        for(Integer i=1;i<dataRecs.size();i++){
            fieldValues = dataRecs[i].split(',');				
            parsedData.add(fieldValues);                
        }   
    }
    public static VOID parseContactFields(String fileName){
		//Make sure the contact list to upsert is empty.
        contactList.clear();
        /*Debug code to be sure contactList is empty. */
        for (Contact thisContact : contactList){
            System.debug(thisContact);
        }
        //Parse the data from the file
        parseFileRecs(fileName);
        proceedFlag = true;
	List<Account> contactAcctList = new List<Account>();
        List<String> AccountNumList = new List<String>();
        String tempVal;
        //Set to test for duplicates
        //Set<Contact> externalIDs = new Set<Contact>();
        //Retrieve all the account numbers from the CSV file
        for(Integer j=0;j<parsedData.size();j++){
            AccountNumList.add(parsedData[j][1]);
            //Debug code
            //system.debug('Acct # added: '+AccountNumList[j]);
        }
        //Query the db for all accounts matching the list of account numbers
        contactAcctList = [SELECT Id, mkfa_AccountNum__c FROM Account WHERE mkfa_AccountNum__c IN :AccountNumList];   
        //Iterate through the records in the file
        for(Integer i=0;i<parsedData.size();i++){
            //Create contact from this row of data
            tempContact.mkfa_External_ID__c = parsedData[i][2];
            //Checking for duplicates
/*
            if(externalIDs.contains(tempContact)){
                system.debug('This ID is a duplicate: ' + tempContact);
            }
            else{
                externalIDs.add(tempContact);
            }
*/
            //debug Code
            //system.debug(i+': Contact External ID: '+ tempContact.mkfa_External_ID__c);
            tempContact.FirstName = parsedData[i][4];
            //debug code
            //system.debug('Contact First Name: '+ tempContact.FirstName);          
            tempContact.LastName = parsedData[i][5];
            //debug code
            //system.debug('Contact Last Name: '+ tempContact.LastName);
            //Get the account # from the file, test it against the list of accounts we queried earlier in SoQL
            tempVal = parsedData[i][1];
            for(Integer k=0;k<contactAcctList.size() && proceedFlag==true;k++){
                if(contactAcctList[k].mkfa_AccountNum__c==tempVal){
            		tempContact.AccountId = contactAcctList[k].Id;
                    proceedFlag = False;
                }     
            }                
            //Add the contact to the contact list
            if(!contactList.contains(tempContact)){
            	contactList.add(tempContact);
                system.debug('Contact added: ' + tempContact);
            }
            else{
                system.debug('Contact is dup: ' + tempContact);
            }
            //debug code
            //system.debug('Added contact: '+tempContact); 
            proceedFlag = true; 
        }  
        //Testing for duplicates. Makes sure the set used to look for dups is the same size as the list of contacts.
/*        if(contactList.size()==externalIDs.size()){
            system.debug('No problems with dups. Proceed.');
        }
        else{
            system.debug('Hold up. There are dups the SS did not find.');
        }
*/
                    //Try to upsert the contacts *****Use external ID
		Database.UpsertResult[] upsertResults = Database.upsert(contactList,Contact.mkfa_External_ID__c,true);		        
/*        try{
            upsert contactList Contact.fields.mkfa_External_ID__c;
        } catch(DmlException e) {
            System.debug('The upsert failed. That is OK. Return to the maze and take this message to guide you: ' +
                         e.getMessage());
        }          
*/
    }
}

#Apex #Duplicates #Contacts #Matching Rules