Provide a way to merge contacts while keeping contacts registered to their TeamRaiser events
When a constituent with multiple records in Raiser’s Edge has their records get merged, one record is designated as a “secondary contact” and is emptied in the process. If this now-empty secondary contact gets deleted, that constituent also gets deleted from Constituent 360. The problem is that if this now-deleted secondary contact was registered for a TeamRaiser event, they will have also been wiped off of TeamRaiser. Cleaning our records and merging contacts is crucial for database integrity, but we a way to ensure that merged contacts aren’t accidentally removed from their fundraising initiatives.
We need this solution to be easy to implement and duplicate (i.e. the solution must be intuitive enough that someone with only basic computer literacy could handle). Many of the employees responsible for key features of the system (like event registration and donation management) only have basic computer literacy.
-
Guest
- Dec 21 2015
- Reviewed: Voting Open
| Area of the Product | Database |
Related ideas
To further this request in Luminate Online, I would add, based on Support Case #00681666, that because Luminate uses the most recently updated record as the master record when processing these merges, it nullifies the original TeamRaiser Personal Page link for participants. Therefore contacts for that fundraising participant no longer have a link for a viable fundraising page.
It appears Luminate does not properly route all info for the surviving record.
A new feature release for the Luminate Online plug in is shipping tonight, February 4th, 2016. This will be available for all hosted clients upon completion of the maintenance, and for all on premise clients after they run the manual install process required with this release only.
One of the included enhancements with this release is the surfacing of the Luminate Online (Team Raiser) username in the plug in when viewing a constituent record. If there is a need to merge a constituent record with an existing Raisers Edge constituent, the username can be selected so that it persists on the surviving record in Luminate Online upon successful completion of the merge. The encrypted password moves along with the username behind the scenes. The end result is that the Team Raiser participant can continue to log in with what they know to be the most current/recent user credentials.
The attached product release notes more eloquently describe this feature and include some screen shots. Please review them and feel free to add additional comments with any questions you may have. I would also like to know if this feature solves the problem for you.
Hi Jovan, I'm not sure if this would be a change to RE or LO so I'm reaching out internally to find out. This has been reviewed but I don't want to change the status until I know it's a fix that must be on the LO side. If not I'll send this over to the RE team on your behalf.
I'll keep you posted. Thanks,
Ken