Duplicate Merge improvements

Aldera Chisholm

I came back from vacation and saw in the “What's New” the improvements to the duplicate merging. Most vitally, the addition that some missing pieces like Opportunities are now included in the merge, and the ability to choose what to do with soft credits, and delete the source record. This seems to solve so many challenges! Has anyone played with it yet, and if so, any feedback? I don't have enough dupes to give it a good test just yet.

Joe Moretti

@Aldera Chisholm I still use for the most part, the workhorse called RE DATABASE VIEW. RE NXT has just a few thing, very few that work better than DATABASE VIEW.

Aldera Chisholm

@Joe Moretti I use both, absolutely depending on what you need.

Alex Wong

@Aldera Chisholm
it is a very good upgrade from what we had. I strongly suggest you try it.

my CRM team has tried it and the feedback so far is great with the exception that the deleted record's constituent id is not being created as an Alias on the constituent record that remains. This is something that was requested in BBcon directly to the person in charge of merge functionality upgrade and we were promised that it will come too. So I am hopeful.

for example: previously web merge does not merge record when both constituent has event participant record to the same event, now it does it no problem

Aldera Chisholm

@Alex Wong That is great to hear. Fingers crossed on the Alias improvement. I found cleaning dupes in Data Health to have such better duplicate criteria so it will be great to complete the full process there. I think it will be much easier to train folks on this system as well!