Answered by:
Depulicating leads and accounts / contacts

Question
-
We have a lot of historical data that was imported into MS CRM. There is however a lot of duplicates that have now appeared between leads and accounts / contacts.
Is there a way the depupe between these entitiesFriday, February 19, 2010 5:04 PM
Answers
-
I sympathize with your dilemma as it is not an easy problem to solve. If you have someone on staff who is proficient with SQL, you could define a set of criteria for that person to query the respective views and pull a list of potential duplicates. Once you isolate the duplicates, you could then have a .NET coder write a simple application that will take all of the IDs for the duplicate records and use the CRM Web services to deactivate those records.
There are lots of ways to dedupe data and none of them are fun. I have found this method to be the least painful way.- Proposed as answer by Scott Sewell, Hitachi SolutionsModerator Friday, February 19, 2010 11:08 PM
- Marked as answer by Jim Glass Jr Tuesday, February 23, 2010 4:14 PM
Friday, February 19, 2010 6:36 PM -
You can set up a duplicate detection rule, for example on the lead company and account name field, that can be used to run a duplicate detection job. No need to write SQL or build anything in .NET -- all the standard features are there.
- Marked as answer by Jim Glass Jr Tuesday, February 23, 2010 4:13 PM
Tuesday, February 23, 2010 2:28 PMModerator
All replies
-
I sympathize with your dilemma as it is not an easy problem to solve. If you have someone on staff who is proficient with SQL, you could define a set of criteria for that person to query the respective views and pull a list of potential duplicates. Once you isolate the duplicates, you could then have a .NET coder write a simple application that will take all of the IDs for the duplicate records and use the CRM Web services to deactivate those records.
There are lots of ways to dedupe data and none of them are fun. I have found this method to be the least painful way.- Proposed as answer by Scott Sewell, Hitachi SolutionsModerator Friday, February 19, 2010 11:08 PM
- Marked as answer by Jim Glass Jr Tuesday, February 23, 2010 4:14 PM
Friday, February 19, 2010 6:36 PM -
damn is this the only way, I was hoping for a simple solutionTuesday, February 23, 2010 1:09 PM
-
You can set up a duplicate detection rule, for example on the lead company and account name field, that can be used to run a duplicate detection job. No need to write SQL or build anything in .NET -- all the standard features are there.
- Marked as answer by Jim Glass Jr Tuesday, February 23, 2010 4:13 PM
Tuesday, February 23, 2010 2:28 PMModerator