Prevent Duplicate Records in Salesforce by Comparing more than one fields

Quick Summary on Logic:

      The below trigger written in Lead object using equals and hashCode Method. This methods are used on uniqueness.  Each hashCode value is unique. 

For example: test@mail.com and Test@mail.com will provide different hashCode values.

Object: Lead

Logic: If Lead record contains same Email and Company Name, then the below trigger will prevent duplication.

Apex Class

1. public class DeDupeWrapper
2. {
3.     public String email;
4.     public String company;
5.    
6.     public DeDupeWrapper(String email, String company)
7.     {
8.         this.email = email != null ? email.toLowerCase() : email;
9.         this.company = company != null ? company.toLowerCase() : company;
10.     }
11.    
12.     public Boolean equals(Object obj)
13.     {
14.         if (obj instanceof DeDupeWrapper)
15.         {
16.             DeDupeWrapper p = (DeDupeWrapper)obj;
17.             return ((email == p.email) && (company == p.company));
18.         }
19.         return false;
20.     }
21.    
22.     public Integer hashCode()
23.     {
24.         return (email.hashCode() * company.hashCode());
25.     }
26. }

Apex Trigger

1. trigger DeDuplicateLead on Lead(before insert, before update)
2. {
3.     Map<DeDupeWrapper, Lead> leadMap = new Map<DeDupeWrapper, Lead>();
4.     Map<String, String> duplicateMap = new Map<String, String>();
5.    
6.     for (Lead currLead: Trigger.new)
7.     {
8.       if((Trigger.isInsert && (currLead.Email != null && currLead.company != null))  ||
9.            (Trigger.isUpdate && (currLead.Email != Trigger.oldMap.get(currLead.Id).Email ||
10.                                  currLead.Company != Trigger.oldMap.get(currLead.Id).Company)))
11.         {
12.            
13.             DeDupeWrapper key = new DeDupeWrapper(currLead.Email, currLead.Company);
14.            
15.             if (leadMap.containsKey(key))
16.             {
17.                 currLead.Email.addError('DUPLICATE CAUGHT...!');
18.             }
19.             else
20.             {
21.                 leadMap.put(key, currLead);
22.             }
23.         }
24.     }
25.    
26.     for(DeDupeWrapper currWrap : leadMap.keySet())
27.     {
28.         duplicateMap.put(currWrap.Email, currWrap.company);
29.     }
30.    
31.     for (Lead lead : [SELECT Email,Company FROM Lead WHERE Email in: duplicateMap.keySet() AND Company in: duplicateMap.values()])
32.     {
33.         DeDupeWrapper key = new DeDupeWrapper(lead.Email, lead.Company);
34.         Lead newLead = leadMap.get(key);
35.         if(newLead != null)
36.         {
37.             newLead.addError('DUPLICATE RECORD ALREADY FOUND');
38.         }
39.     }
40. }

Reference: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/langCon_apex_collections_maps_keys_userdefined.htm

equlas and hashcode method example in Salesforce

Here is the simple real time example of Equlas and HashCode method usage in Salesforce,

You can compare more than one field in SOQL Query for bulk insert and update operation. Based on the comparison search result you can do your logic. The below example will explain the functionality as follows,

Case Object:

1. Status(Standard Field)
2. Description(Standard Field)

Account Object:

1. Name(Standard Field)
2. AccountNumber(Standard Field)

Scenario:

While insert/update Case record, if both status and Description field matches to the Account name and AccountNumber means, i need to update the case with matched account.

For e.g:
Case Status: Arun
Case Description: 123

Account Name: Arun
AccountNumber: 123

The above case record matched with account field values. So in this scenario need to update account field value on case. If Multiple/No related accounts found, then I just updated another field in Case.

Wrapper Class with Equals and HashCode Method:

1. public class PairStrings {
2.     String subject, description;
4.     public PairStrings(String str1, String str2) {
5.         subject = str1;
6.         description = str2;
7.     }
9.     public Boolean equals(Object obj) {
10.         if (obj instanceof PairStrings) {
11.             PairStrings p = (PairStrings)obj;
12.             return ((subject==p.subject) && (description==p.description));
13.         }
14.         return false;
15.     }
17.     public Integer hashCode() {
18.         return (31 * subject.hashCode()) ^ description.hashCode();
19.     }
20. }

Trigger on Case Object:

1. trigger CaseTrigger1 on Case (before insert, before update)
2. {
3.     Set<String> subjects = new Set<String>();
4.     Set<String> descriptions = new Set<String>();
6.     for(Case currCase : Trigger.New)
7.     {
8.         subjects.add(currCase.subject);
9.         descriptions.add(currCase.Description);
10.     }
11.    
12.     Map<PairStrings, List<Account>> accountMap = new Map<PairStrings, List<Account>>();
14.     for(Account currAcc : [SELECT Id, Name, Description, AccountNumber FROM Account WHERE Name in:subjects AND AccountNumber in:descriptions])
15.     {
16.         PairStrings ps = new PairStrings(currAcc.Name, currAcc.AccountNumber);
17.        
18.         if(!accountMap.containsKey(ps))
19.         {
20.             accountMap.put(ps, new List<Account>{currAcc});
21.         }
22.         else
23.         {
24.             accountMap.get(ps).add(currAcc);
25.         }
26.     }
27.    
28.     for(Case currCase : Trigger.new)
29.     {
30.         PairStrings ps = new PairStrings(currCase.subject, currCase.Description);
31.        
32.         if(accountMap.containsKey(ps))
33.         {
34.             if(accountMap.get(ps).size() > 1)
35.             {
36.                 currCase.Account_Status__c = 'More than one account found';
37.             }
38.             else
39.             {
40.                 currCase.AccountId = accountMap.get(ps)[0].Id;
41.             }
42.         }
43.         else
44.         {
45.             currCase.Account_Status__c = 'No matching account found';
46.         }
47.     }
48.    
49. }

Reference: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/langCon_apex_collections_maps_keys_userdefined.htm

Salesforce Summer'15 Maintenance / Release Exam Notes

       Here is the quick summary of Salesforce.com Summer'15 quick glance of release notes. This will definitely helpful for your Summer'15 Maintenance exam.

Chatter

Edit Feed Posts and Comments:

It Ensure that your feed posts are accurate and up-to-date with feed post editing.

"Allow users to edit posts and comment" chatter setting option is enabled by default. To verify go to the below path in your salesforce organization,

Setup | Customize | Chatter | Settings 

The following Profile Level Permission available to handle the edit options on post,

1. Edit My Own Posts 

2. Edit Posts on Records I Own (It's disabled by default for existing profiles) --> Users who have Modify All Profile Permission in profile can edit all post and comments, regardless of this permission.

Chatter Free, Chatter External, and Customer Portal Users do not have the ability to edit their post and comments.

Reference: http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_chatter_feeds_edit_posts.htm

Share Any File With Library:

Users can share Chatter and external files with Library. Using this feature you can share the Files you own, Shared Files, and External files.

This feature is disabled by default, to enable this navigate like below,

File user interface allows sharing files with libraries.

Reference: http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_chatter_files_share_any_file_with_library.htm

Sync Content Files

All your files from content libraries, including private files, can be synced in Chatter. Using this feature, users allows to sync their files from library. 

"Enable files sync" option from the above navigation.

Reference: http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_chatter_files_sync_content.htm

Salesforce Files to Folder

When you sync a file in Chatter, now you can sync it to a folder.

User must need to install app in their desktop as well salesforce file sync must be enabled.

Reference: http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_chatter_files_sync_folders.htm

Managing Custom object records added to the Groups:

It allows which custom object records end users can add to chatter group.

"Allow in Chatter Groups" option is available in object setting. If you create/edit object you will find the below option.

Reference: http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_chatter_groups_custom_object_add_flag.htm

Force.com

Set up Assistance:

It's now available for newly activated organization. It provides helpful videos and guides in importing sales data and basic configuration. Set up Assistance option available in the side bar.

Data Loader:

Data Loader now available on Mac OS

Login Access Policy:

From Summer 15 onward, "Administrators Can Log in as Any User setting" allows login as any users without need of end user support.

Permission needed for this feature is,

1. The The Modify All permission enabled for administrator.

2. The View and Setup configuration permission enabled for delegated administrator. 

Reference: https://help.salesforce.com/apex/HTViewSolution?urlname=any-user

Mobile

Customize actions in the salesforce1 Action bar:

Developer can override the predefined actions and specify separate set of actions to appear in salesforce1 web interface.

1. Action category pallet renamed to quick action.

2. New category named as Salesforce1 Actions.

3. Actions in the publisher section is renamed to Quick Actions publisher section.

Reference: http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_mobile_salesforce1_newfeat_actionbar_customization.htm

Lightning App Builder:

It's a point and click tool that make it easy to create custom page for salesforce1. It provides the following features,

1. Single page application.

2. Dashboard style application.

3. Applications to solve a particular task.

Reference: http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_mobile_salesforce1_newfeat_appbuilder.htm

Services

Macro:

Support agents who use Case Feed can use macros to complete repetitive tasks—such as selecting an email template, sending an email to a customer, and updating the case status—all in a single click. Macros save time and add consistency to support agents’ work.

The following enhancement are available from summer 15,

1. Run Bulk macro on multiple records at the same time. 

2. Search and attach articles to cases.

3. Post to social networks.

4. Replace field value in Case.

5. Insert field values in case.

Reference: http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_macros.htm

Add Report Charts in Console Side bar:

1. You can add Matrix or Summary Report.

2. Report folder must be shared who accessing the specified report.

For this, You need to add the report in page layout, and you cannot move the side bar report between sandbox and production. It's not avail on Meta data API.

Reference: http://releasenotes.docs.salesforce.com/en-us/summer15/release-notes/rn_console_report_chart_setup.htm

Thanks for reading this post...!

Exam Questions:

Dev 401 Summer 15 Maintenance 

Admin 201 Summer 15 Maintenance