Hi all,
I have a business requirement that states that whenever a user enters a new LEAD it should look for duplicates on the ACCOUNTS. The idea is to prevent sales people to enter leads when the company is already a customer.
We have created a duplicate detection rule, with BASE RECORD = LEAD, and MATCHING RECORD = ACCOUNT that checks for an exact match between Company Name (in leads) and Account Name (in Accounts).
When a new lead is entered the behaviour is what I expect. But, when the user qualifies the lead into an account the system throws a duplicate detection warning that is very strange: it says there is a potential duplicate, but without identifying the potential duplicate (that part is left blank and says "potential duplicates: none").
After several tests, I disabled this rule, and qualification is again posible, making me believe the problem lays in this rule. If so, it also means that the rule will be applied not only upon creation but also on qualification, which will then result in always existing a duplicate (because qualifying is exactly that: creating an exact match on the accounts entity)
Can anyone clarify this for me ?
Much apprecciated.
Romeo