Allow for detection of dup non constituent records and the ability to merge them in RENXT. A bonus would be to select multiple from a list to merged together or w/ a constituent record/
Duplicates of non-constituents is horrible in Web View - so many are created during event registration and there does not seem to be a way to merge these non-constituent records together. Database View has a plug-in where we can merge non-constituents. Without something similar in Web View, there is and will continue to be a lot of these orphaned records that essentially become useless and "junk" up the system.
We have so many duplicates in our non constituent records. I would love to be able to clean these up in NXT without having to change all of them to constituents first then merging them. We would like to be able to keep them as a relationship record
We use the non-constituent merge utility a lot - to merge employment records that we have imported. I presume this plug in will not be migrated, so we do need equivalent functionality to handle these. I think if non-constituents could be handled through export / import we could merge them manually, that would be a half way house, but ideally normal bulk merge functionality would be invaulable
I am surprised there are not more votes for this.
Duplicates of non-constituents is horrible in Web View - so many are created during event registration and there does not seem to be a way to merge these non-constituent records together. Database View has a plug-in where we can merge non-constituents. Without something similar in Web View, there is and will continue to be a lot of these orphaned records that essentially become useless and "junk" up the system.
We have so many duplicates in our non constituent records. I would love to be able to clean these up in NXT without having to change all of them to constituents first then merging them. We would like to be able to keep them as a relationship record
We use the non-constituent merge utility a lot - to merge employment records that we have imported. I presume this plug in will not be migrated, so we do need equivalent functionality to handle these. I think if non-constituents could be handled through export / import we could merge them manually, that would be a half way house, but ideally normal bulk merge functionality would be invaulable