#Leads0 discussing

The dummy field workaround works but it's a lot of manual steps for what should be a simple matching operation. The bigger problem is that Salesforce treats matching as exact-or-fail. 

I'd recommend using a semantic matching tool. Sharing the one I'm building:

Here are approache to manage multiple emails for leads in Salesforce, preventing duplicate leads and ensuring all contact information is captured:

Utilize Duplicate Management Rules and Merge Function

1. Adjust Duplicate Rules: Modify your existing duplicate rules to allow leads with the same name but different emails.
2. Merge Duplicates: After multiple leads are created with the same name and different emails, use the Merge Leads feature. This allows you to combine these leads into a single record, preserving all associated information like emails.
3. Workflow Automation: Consider creating a workflow that automatically merges duplicate leads based on specific criteria (e.g., name and email combination).

Hi  Wayne Gladman,

Try this formula,

IF((Lead_Age__c <= 5 && Lead_Age__c>=0), 10,  IF( (Lead_Age__c <= 10  && Lead_Age__c >=6) , 6,  IF((Lead_Age__c <= 35 && Lead_Age__c>= 11), 9,  IF((Lead_Age__c <=60 && Lead_Age__c >= 36), 4,  IF((Lead_Age__c <= 90 && Lead_Age__c >= 61), 2,  IF(Lead_Age__c >=91, 8, null) ) ) ) ) )

Hi @Anne Kuczynski,

I see that at the moment your duplicate rule alerts and/or blocks the creation of the lead, so it doesn't come through. Are you able to identify via a certain field, all the leads that are part of this email campaign? If that's the case, you could create another duplicate rule (using the same matching rule) that does not alert nor block of the duplicate - it will only create a "Duplicate Record Set" Record with its child "Duplicate Record Item" records. You will need to create a filter in this duplicate rule so that it only applies to the relevant leads (and you will also have to filter the existing duplicate rule so that it doesn't apply to these leads, as you want these to pass through).

At the same time, you need to create a record-triggered flow on the "Duplicate Record Set" object, and in the Condition set that "Duplicate Rule ID" is equal to the ID of the new Duplicate Rule that you just created before, so that the flow only triggers for this case. In the flow you would then have to do a Get records to obtain the "Duplicate Record Items" for this Duplicate Record Set, so that you can figure out the Ids of the Leads (one will be the old Lead and one will be the new one, you can check that by CreatedDate. Once you have identified the old Lead Id, you can do the flow actions to assign the current campaign to this lead and reset the status to new, and finally add a delete element to delete the new Lead that just got created, so that only the old lead remains.

Hope this helps, let me know if you need clarification!

Sorry, 

I think I didn't express myself well. The validation rule is necessary, but this massage in front of the real message was not supposed to be appearing. I'd like to remove it and let only the message for de user. 

The massage:

"ConvertedLead failed. First exeception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION. Erro de validação em contato:"

if not possible to remove the message. I'd like to understand why.

Thanks for now

Hi @Arnaud Fournier,

Please access Data Manager > Connections > SFDC_LOCAL > Edit Objects. You will be able to check if the Created Date is selected or not.

TDTM_Lead is actually an Apex trigger.  But you are correct, there are no out-of-the-box TDTM handlers for the Lead object.  The TDTM_Config_API class is not a TDTM handler itself, it's more of a dispatcher to the specific TDTM handlers.

It sure feels like an object permissions error, even though you say you've set all the correct permissions.  You should not need to set permissions on the Apex triggers / classes since those are running in system context already.