Just to clarify - did you just want all the logic to only apply to the second list of record types, or did you want all leads to be checked, but only rejected if there a existing company for leads with a record type in list two...? Sounds like you only wants leads with Record Types in the second list to be checked for dupes?

If so, there are a couple of things to consider. As a previous post mentioned, triggers only have the Record Type Id - so if you want to when we filter by record type name, you need to match the Id with the name - which you can do a with a describe call on the lead object - I can post an example if you need one.

But I am thinking a better approach would be to store the Record Type Ids you want to be checked in a custom setting. That way, if a new record type is added tomorrow, you don't need to update your code - you just need to add a new record to the custom setting, and it will be included in both the initial check and the query.

Let me know, and I can post some snippets to help you get there...   

HI BritishBoyinDc



I just want the logic to apply to those record types listed. So if a Burger King Limited is saved on the “FDMS Lead Generation or FDMS Sales Lead, and a new lead of Burger king Limited is trying to be saved on the FDMS Lead Generation or FDMS Sales Lead record type, then the trigger would advise the user, that that lead is already in the database under those two record types

What do you think be the easiest given my situation above ?

So I would do something like this...create a new Custom Setting, and store the Record Type Ids you want the logic to apply to in the default name field for that setting.  I would then add a check in the first loop to see if the record type for the lead in the trigger is in that setting - if so, go ahead and process it. 

I would then also update the search query to query for leads with record types stored in the setting. 

It ends up looking something like this, where the new setting is called Manage_Lead_Dupes.  That way, you can just add a new record type to the setting, and it will be included in the logic. Note - in testing this, it is important to store the 18 character version of the Record Type Id (the one the API uses) in the Custom Setting, otherwise they won't match. 

Trigger DuplicateLeadPreventer on Lead
                               (before insert, before update) {
 
 //Get map of record types we care about from Custom Setting
 Map<String, Manage_Lead_Dupes__c> leadrtmap = Manage_Lead_Dupes__c.getAll();
 
 //Since only certain leads will match, put them in a separate list
 List<Lead> LeadstoProcess = new List<Lead> ();
 
 //Company to Lead Map
 Map<String, Lead> leadMap = new Map<String, Lead>();
 
    for (Lead lead : Trigger.new) {
     
     //Only process for Leads in our RecordTypeMap
         if (leadrtmap.keyset().contains(lead.RecordTypeId) ) {
                               
        // Make sure we don't treat an Company name that 
       // isn't changing during an update as a duplicate. 
   
              if (
                 (lead.company != null) &&
                 (Trigger.isInsert ||
                 (lead.company != Trigger.oldMap.get(lead.Id).company))
                 ) 
                 {
                                       
                    // Make sure another new lead isn't also a duplicate 
           
                        if (leadMap.containsKey(lead.company)) {
                            lead.company.addError('Another new lead has the '
                                            + 'same company name.');
                        } else {
                            leadMap.put(lead.company , lead);
                            LeadstoProcess.add(lead);
                        }
                }
    } //end RT If Check
    } //End Loop
               
    /*
     Using a single database query, find all the leads in 
     the database that have the same company address as any 
     of the leads being inserted or updated. 
   
   */
   
    Set<String> ExistingCompanies = new Set<String> ();

            for (Lead l: [Select Id, Company from Lead WHERE Company IN :leadMap.keyset()
                             AND RecordTypeId IN :leadrtmap.keyset()]) {
                          ExistingCompanies.add(l.Company);
                }

    //Now loop through leads to process, since we should only loop if matches
    for (Lead l : LeadstoProcess) {
        if (ExistingCompanies.contains(l.company) ) {
             l.company.addError('A lead with this company '
                               + 'name already exists.');
        }
    }
}