Convert the data on NetCommunity tab when merging RE constituents
If "Constituent A" has been emailed out of BBNC, whether or not they are linked to a BBNC User Account, this email information is tracked on the NetCommunity tab of their RE Constituent Record. If an organization merges Constituent A's record into "Constituent B's" RE record, the NetCommunity data from Constituent A's record is lost and not transferred. All other information, i.e. gifts, relationships, etc, all survive the merge. The NC data should be handled the same.
-
Guest
- Apr 23 2012
Related ideas
I just spent some time speaking with Support about this very same issue. Both records are unlinked in BBNC. The data stored in the NetCommunity tab in the duplicate record would not transfer/merge into the "real" record (the record I need to retain). The NetCommunity data found in each record was not identical. So, after merging these records, I deleted the duplicate record, thereby losing the NetCommunity data stored there. :-(
I just noticed that the net community email history doesn't merge. That is a problem for us as well
If keeping a clean database is important then the lack of this functionality is a serious fail.
The Net Community Tab and it's information are invaluable to us. Even the Execute team uses this tab to see what emails were sent. I was shocked when one of my coworkers pointed out that the email information doesn't go when merging. It's been on my to do list to submit for discovery - THANK YOU for posting - Wish I could give it 20 votes instead of just 3
I support this suggestion 100%.
I would add to this that following the merge and loss of NetCommunity data the red check indicator still displays on the NetCommunity tab - despite the fact that there no longer is any data there. This should also be considered when evaluating this request.
I had the same problem, but I realized that after a short period of time (for our system, it was about 5 minutes, but it may vary depending on your syncing scheduling, up to 24 hours) it should generate an automatic NetCommunity "Sign Up Request" noting that the user was deleted or merged. If you process this transacation, it should relink the NetCommunity information to the new merged record. Again, this will take the same amount to show up on the record (as in, it may still appear blank but if you wait a maximum of 24 hours and check again, it should be there). We have tested this on our system and it attaches all of the historical NetCommunity details to the new record.
I realize that this may not be considered a solution by some, as it requires multiple extra steps rather than simply converting the information in the merge. However, I wanted to point out that the NetCommunity information is not lost, but simply sits in the NetCommunity online user gallery unlinked to an RE record until the automatic process kicks in to send a new Sign Up Request. Not sure if this is new functionality or simply something I hadn't noticed before, but you should be able to try it out and see the new Sign Up Request come through in order to relink the information. Would be nice to see an official response to this to explain the evolution of this feature!
NetCommunity data should have it's own option within the Merge Constituents function. I've only been using BBNC for a few months and we've already encountered a situation where this was needed. I hope it doesn't become a recurring problem.