What's New In Raiser's Edge NXT The Week of April 28

Published

This week, Raiser's Edge NXT introduces a new option to help you merge duplicates.

Quickly merge known duplicates. To help you more quickly address duplicate records, you can now merge a pair of records under Tools, Data Health. When you view the list of possible duplicates, you can now select Select records to merge and search for a source and target record. Previously, you had to review the records before you could merge them.

This can be useful if you know for certain that two records are duplicates and don’t need to review each record individually. For more information, see Possible Duplicates.

News Blackbaud Raiser's Edge NXT® Blog 04/28/2020 5:15pm EDT

Added by Kimberly Coughlin

8 Comments

Paula Koetter May '20

Hello again Dwaye! Thanks for the suggestion. You are correct that we don't bring in that information. Sounds like a great suggestion for the idea bank if you'd like to add it there!

Dwayne Dipasquale May '20

I also notice that when you merge on NXT it doesn't bring over the deceased person's honour/memorial tab information, why is that?

Paula Koetter May '20

Hi Dwaye! Thank you for your feedback. I've brought this up to the development team and they will add it to their list. They thought it was a great suggestion. Thanks again!

Dwayne Dipasquale May '20

When merging in datrabase view, having the target record open once the merge is completed so we can then add our notes and put the former ID in Alias, was a great function; why doesnt this happen in webview?

Paula Koetter Apr '20

Hi Jaclyn! You are correct, the merge marks the source record inactive but does not delete it. To delete records, you have to go to database view. To help you with this, you can create a list of merged duplicates so you can delete them all at once in database view. This help topic covers the details under "Delete merged source records." Hope that helps!

https://webfiles.blackbaud.com/files/support/helpfiles/rex/content/test/content/data-review-merged-duplicates.html

Jaclyn Whitelock Apr '20

My issue is that it doesn't delete the source constituent, just marks it as inactive. I can't find any setting to delete the source constituent, like there is in the database view. Am I missing something?

Paula Koetter Apr '20

Hi AnnMarie, thank you for bringing this to our attention. The new merge functionality is intended to work exactly as the previous merging worked, so this doesn't sound like the intended behavior. Our development team is going to look more closely at this and I'll let you know what they find. Thanks again!

AnnMarie Schell Apr '20

Coincidentally, I am in the process of "quickly [merging] known duplicates." What I find is that the merge is duplicating constituent codes in the target record. It doesn't help to deselect the field when there is a constituency code I need merged from the source into the target; especially if the target has a more complete record otherwise. If this has something to do with the dates, will other fields with associated dates be affected? Any solutions?