As always with Blackbaud, we've encountered this same issue and their solution is to vote on an approaching 4 year old idea asking for it to be corrected. I echo everyone's sentiments that this is a ridiculous oversight. The "solution" I was given was to let donors know to write only one name in a tribute section, not "Joe and Jane Smith." Would be great if there was some kind of update on this or an approval process before the system automatically creates new records.

Giving Tuesday donations and your auto-linking has destroyed my clean database. I spent days going back into each donation and making sure there wasn't a duplicate constituent record or a tribute that was a duplicate. We are a relatively small organization but this has been a disaster. John M Smith, '31 (class of '31) is now listed as last name '31 and first name as John M Smith. Or Jack & Marcia New have an account under John New. Now they have a second account that I have to merge and/or delete. This is terribly frustrating! Unless this is changed back, I will go back to OnlineExpress because donor cover didn't bring in the amount they have to pay me for the hours of cleanup or the frustration!

I also feel like this is just one more way that we are being pushed into the next tier of pricing - add more records to our account that we don't need!

I also agree with everyone else. The only reason I use NXT for donations is because the donor can choose to pay the credit card fees. I wish that feature was available in OLX.

I found a pair of duplicate records in database view. But they don't show up in the Tools/DataHealth/Duplicates area of web view. REASON: The duplicate record was added by "NXT System User (Tribute Service)", which I guess means that it was created when someone made a gift through an RENXT Donation form in memory of someone. When they made it in memory of someone, that someone had a new record created for them with first name 'Dr. Karen'. So the Data Health doesn't recognize "Karen" and "Dr. Karen" as potential duplicates. This has created issues for us in our tribute reporting to the family! I sure do hope that when BB rolls out tribute management in the web view, that duplicate management is part of it!

Please make this change. It is creating pointless busy work to merge or delete constituents and adds no value otherwise.

Yes, please make this change. As others have said, it is creating unnecessary work. This is one of many reason why we don't like to utilize the NXT Forms for donations as well.

Amen and AMEN! We spend literally an hour each month deduping our database from this specific issue! Before we switched to NXT we were using Net Communities, the way that matched and let me manual override the match if necessary or autocreate a record worked GREAT! Steal your own software code from Net Communities and relaunch it with NXT.

Yes, please provide the type of review & control over the consitituent matching that exists in OLX.

Argh! Yes! Please allow for a similar process to what OLX has for these gifts. We're doing a big giving push this week, and I'm spending more time tracking down these duplicated records than anything else! You have the duplicate matching capability for small differences, at the very least, use that to process the gifts!

This is one of the reasons we stopped using the NXT Donation Forms - it's not sustainable.

Allowing us to search for a match or allowing the system to have the ability to match on selected criteria would be great.

I went with the Just Giving integration to streamline some data entry. This is not the case with creating all new donors in the process. Please correct!

Agreed. The system is creating donor records that are already in the database for reasons that are not warranted. For example, if the new gift record has a donor with a middle initial but the original record does not have a middle initial, but all other information matches (i.e. the preferred address, the email address, the phone number) the system should not create a new record. It should attach that new gift to the original record. This is frustrating especially when we have hundreds of gifts coming in every day. WE are constantly trying to merge duplicate records because of this. PLEASE DO SOMETHING ABOUT IT

Agreed. Create extra, unnecessary work.

I am more time than necessary merging and deleting duplicate records because there is no "fail-safe" built in. Please correct this!