When merging records in webview add ability to delete source record at the same time
This would make my job much easier! When new alumni register for an event, they frequently provide me with a preferred email rather than the one assigned by the university, so a duplicate record is created because it searches for email matches. I can easily find duplicate records in RE NXT and merge them, but cannot delete the source record in NXT as I can in the database view. This creates much extra work because I hate duplicate records!!!
-
Guest
- Jun 23 2021
- Shipped
Related ideas
Has something changed recently? If we only merge records in NXT web view, information from the database was not pushed over and ultimately, lost.
We had to merge first in web view to preserve information like attachments and then merge records again in database view. Once both merges were complete, the duplicate record could be deleted in DB view.
Did BB make changes that perhaps I missed?
Agree with everyone here and in an older thread for this same idea! I have to manually delete the duplicate accounts in Database View every time. Occasionally, I'll forget to do this step right away and get confused messages from my team about "duplicate accounts" that I thought I had cleared up.
Agree! This does not promote a clean database!
Agreed, considering the inability to view items like Attachments in database view, it is becoming clear that best place to merge is in NXT. However, not efficient to have to go to database view to delete records, but leaving these as inactive (i.e. really duplicates) could have a direct financial cost during contract negotiations. Would really appreciate making this a priority.
Agreed, needlessly tedious to have to go into Database view to delete inactive records after merges (and we do want them deleted 99% of the time)
100% agree - I wasted much more time than anticipated when I didn't realize that NXT just makes the source record inactive. If merged in NXT there is no way to keep it from pulling both records, even though one is inactive - you could merge those two records until your face turns blue with no indication that it worked, unless you look deep within the Tools. In addition, our organization is trying to clean out constituent records to reduce the number we have to pay for when re-upping our contract, and all these in-actives make for extra records that should otherwise be deleted.