Hello
I've had several issues sofar with duplicate detection in CRM 2013 and would like some advice/ideas.
One of them was an error when qualifying the lead as a new contact to an existing account or as an existing contact on an existing account (using the parent account / contact fields for the lead).
This was resolved by unpublishing the "contacts with same first and last name" rule. In the case where the contact exists I can maybe understand that this might bother the process (even though the 'parent contact/account' is an out of the box functionality and the duplicate detection rule is one of the standards that came with the install so I would have thought this would work together). But in the case where the contact doesn't exist yet I don't see why this rule would cause a problem!?
The error message said "There is no active transaction. This error is usually caused by custom plug-ins that ignore errors from service calls and continue processing" - we do have one plugin that calculates discounts and VAT on the opportunity but it doesn't cause problem in any other case of lead qualification and unpublishing that specific contact duplicate rule makes the error go away...
Any thoughts about this? Just curious, as we can live with me doing manual duplicate detections on contacts once in a while (even though not optimal)
Another issue we're seeing is a duplicate warning when wanting to qualify a lead to a contact / account, even though there are no duplicates for this lead in the system. This is slightly annoying and lessens my trust for the actual duplicate detection rules, but this also blocks our automatic conversion in our support interface: Whenever a person that is at the moment a lead in our crm fills in our support webform, a duplicate check is performed on our side on emails, names, company names and our own website ID and if nothing found the lead is converted into account/contact and a support case is created.
Any ideas on this "false" duplicate warning?
thanks! best regards
Leopoldine