Update on this available?

This was created in 2015, has over 200 votes, yet this isn't planned or even under consideration??? You have this capability already built in RE, why can you not utilize that for the education side??? We MUST be able to merge records that are not showing up in the possible duplicates area and we MUST be able to control more of which record is the target and we MUST be able to bring over documents.

I'm running into this issue and am trying to figure out what piece of information is mismatched so that the users will show up in potential duplicates to no avail. What a waste of my time!

How has this been up for 8 year and there has been no update or anything? Blackbaud, we need an update this.

This is critical!! I just came across two users this morning alone that weren't in the potential duplicate area, but were obviously duplicates! You have this capability in Raiser's Edge, why is it not in core? The merging of duplicates should be set up similar to RE NXT where you can choose who to merge and exactly what should be brought over. You also have the capability of choosing the target record....these are all SO important!!

Still waiting for this to happen.

Can you imagine how much easier our lives could be if this idea was implemented!?

Any update here?

This seems like low-hanging fruit. The hard part is already done. Just give us a little bit of UI to choose two records to merge.

The payback would be HUGE! We spend a crazy amount of time dealing with duplicate records that somehow slipped by the magic "Manage potential duplicate users" screen.

Ditto on the ability to choose which credentials to maintain in the resultant record.

I would love to see a feature similar to RE (both db and web view) where you select the two records that you know are duplicates and then determine which data needs to be transferred to the "master" record which will become the new record.

Including the ability to choose login credentials is critical. A separate idea is located at https://blackbaudk12.ideas.aha.io/ideas/K12CO-I-3015 for it. With how the record merge (either through core or through an admission application or inquiry processing) keeps the older login information. That is backwards to the reality that most of our admission duplicates are people who inquired or applied at some time in the past and don't realize that they are in the system or no longer know their credentials. In most cases the older login has been disabled because they are Parent of Past Candidate. It has the potential for a bad parent/customer experience for the user if the person merging the accounts forgets to go back and update the credentials accordingly.

If you are updating the merge duplicate tool, I would love to see the ability to choose which username/login with a check box. We have alums, most of whom have disabled logins and legacy accounts, that lose their newly created blackbaud ID when we merge the record because we have no way to choose the new login information.

As we are nearing the end of 2022, has there been any progress on this? I spend an incredible amount of time manually moving files, notes, etc over to one record so I can delete the other duplicate record. Thank you!

YES! We should be able to merge records that aren't showing up in the potential duplicate list because it definitely does NOT catch half of what I need merged. There should be a force merge option.

Hi Kelly, we are closer! We have this slated to be worked on toward the end of 2022. I don't have a lot of details yet, but as we get closer, I'll be sure to update the group.

Thanks,

Sarah

Are we any closer to a solution for this issue that affects all schools?

Why is this taking so long to be implemented? I too have been spending a rediculous amount of time identifying and merging records that the Potential Duplicates tool does not recognize. I try all the 'fixes' recommended by the KB articles and have spent quite a bit of time on support chat's but not really getting the help that is needed for this issue. The difficulties with manually transferring vital data is also a piece of the problem. If two records cannot be merged, some of the information cannot be transferred accurately which prevents us from deleting the duplicate record and risk losing vital data.

I've been spending a ridiculous amount time identifying and merging records that BB isn't recognizing as duplicates. Please give the users a way to manually select records to be merged. At the very least expand the fields on which you identify potential duplicates such as date of birth. You're missing so many potential duplicates and we then have to manually merge them which is incredibly time consuming. It's happening here nearly daily and that kind of wasted time is time we're not doing more important work like filling the school.

Oooof. Nothing like seeing a fantastic idea sit in the ideas portal for over 5 years. :(

We're now six years into this and still don't have this option. This is absolutely necessary to keep a clean database. Please implement this!

this was suggested over 5 years ago.....we need this to happen. You can do it in RE, so you should be able to do it here too!

Even if there was a way to flag records to be included (or re-included in the case of "leave records sparate" being pressed incorrectly) in the "Potential Duplciates" area would be helpful