Hi again @Sarah Thomas . Unless it's a big import with masses of dupes, I prefer to let them be created. It's a headache, but for 20 or 30 dupes it isn't too bad. When merging records you can choose which data to keep from either (or any of the 3) dupe and it's the safest bet for good clean data. It's worth the effort to get clean data up front. In fact there ARE cases where any dupe process makes mistakes and combines two records that shouldn't be (I had a father and son who lived next door to each other with the same names and we had no email data - they almost got treated as one record).
To get the dupes back, just turn the duplicate rule (or rules) back on and run the import. Try again with the sample and make sure it's recording the duplicates. Once that's done to your satisfaction, run larger sets. Start with 50-100 records or so, then move on to more. Note the system has some limits and I've found for the import tool, 1,000 to 2,000 is the realistic limit, but practically it's often more like 500 or so depending on what you're importing. With processing like what the NPSP does when moving the records in the final step, you might find even tighter limits. This is because of back-end limits on the processing that's done on the back end.
29 respuestas
