nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Potential Duplicate Users" vs. "Duplicate Constituents"

Morgan Kunze

Found a report in the General User Management category called “Duplicate Constituents." On it there are absolutely some genuine dupes (in addition to some that are not actually duplicates, eg. father and son with same name). I'm curious why these show up in this report, but not in the Potential Duplicate Users task. Does anyone know any tricks here that will save me having to manually merge and delete duplicates?

Find more posts tagged with

Comments

Jess Moxsky

Morgan,

Based on my own double-checking, the two views should contain the same constituents. One thing you may be seeing is that the report is alphabetized by last name, while the Potential Duplicate Users tasks lists the most recently-added users first.

The Potential Duplicate User tool also collapses any additional potential duplicate beyond the second record into a dropdown menu, so it is likely you will see more entries in the Duplicate Constituent Report than in the Potential Duplicate User tool.

Remember as well that un-merged records (left separate) will not populate in the 30-Day History on the Potential Duplicate Users page.

Hope this helps!

Morgan Kunze

Thanks for the speedy reply, @Jess! Your point about the users left un-merged is a good one - some of the folks on the Duplicate Constituents report may have been affirmatively left separate. However, in the constituents report, there were a couple of pairs on there that were not present in the Potential Dupes task at all - one of which had identical contact info, email, phone, relationships, and first and last name. I'm guessing this was an artifact of some kind of error in our initial user import. Just surprised it didn't show up in the dupes wizard!

In general I wish there were a way to merge two constituents/users in Core, outside of the Potential Dupes task. It shouldn't be too easy - so we can't do it on accident - but easier than having to move info and delete a user by hand.

Bryan Lorenzo

@Morgan Kunze ditto on wishing there was an easy way to merge duplicates that don't come up in the potential duplicate user tool. There was a way for us to do this in Education Edge and it exists in Raiser's Edge… but no way to do it in the Education Management products. I'm still not really sure after many years on the criteria for it to pick up duplicates.

John Ronan

Ditto Ditto on being able to merge things at will.

I know this was an “idea” years ago. I'm frankly surprised they haven't just implemented it after all this time. Since the mechanics are there in the duplicate page, it should be a layup.

[Frustrating: once again, something we were doing 15 years ago in Edge…. :-( ]