We have duplicate detection rules on contact on First Name-same first 3 characters, Last Name-same first 5 characters and Account-Exact Match.
When a first and last name match an existing contact, even though the Account does not match, and is being converted from a lead to a contact, the user is prevented from creating the record because "a duplicate of the current record already exists". Even though it doesn't meet the rules.
Why does it prevent the record from being created rather than giving a warning?
When a first and last name match an existing contact, even though the Account does not match, and is being converted from a lead to a contact, the user is prevented from creating the record because "a duplicate of the current record already exists". Even though it doesn't meet the rules.
Why does it prevent the record from being created rather than giving a warning?
