Potential Duplicate Users feature merge with a better warning message
I had attempted to merge the accounts of past student with a new Candidate record for the same User since he is reapplying to the school. However, I kept getting an error message because old records are still attached to the original User ID for the past student.
I feel that it would be helpful if the Potential Duplicate Users feature merged accounts more seamlessly, including old student records ( ie. report cards, transcripts, etc) between User accounts. When Potential Duplicates are merging records, I find it confusing and disappointing that new User IDs cannot not be merged with old User IDs belonging to the same person, simply because old records were attached to the old/original User ID (ie. reports cards, transcripts, Learning Profiles, etc.).
It would be more beneficial for the Potential Duplicates to blend duplicate users easily with all previously existing records. Perhaps a warning pop up and Confirm button can be implemented that would ensure the Platform Manager understood when an old User ID has previous information attached and that the action is irreversible.
-
Guest
- Aug 27 2015
Related ideas
The merge for core should be set up similar to RE where you can choose exactly what info needs to be brought over....including files, events, anything
One pattern I noticed is if there are duplicate/past records for both a student and a parent, it will never let me merge the parent, only the student. This was discovered by trial and error. Not sure if anyone has that issue. So a duplicate parent record has to be made, and then has to be deleted immediately.
When we are prompted to merge a duplicate record when processing an application (typically, for a parent of a candidate who is also an alum with separate records), it would be really helpful if we had the opportunity to choose which credentials (user name and password) to assign to the merged record as opposed to only being able to select the individual's oldest account credentials. We want the choice to select which user id (with the associated password) they can use moving forward. While we can update their user id to their new user id on file, there is no way to "transfer" the password they previously created with their newest account.
Just commenting again in the hopes that it bumps this topic up. Still seeing "cannot be completed without further action" as the error message when attempting to merge duplicates, with no indication of what action is needed. In one recent case, the record I hope to delete has no associated forms, relationships, or enrollments... and the non-specific error message gives me no direction as to how to "fix" this error.
It's been four years that this request has been out there. No Progress?
We need to be able to proactively merge records as well. It's very common to not know a user is a dupe until they've been in the system a while. By then, if you've not chosen to merge them, you apparently never can.
This thread is now over 3 years old- any update?
My main issue is that it doesn't tell you WHY it can't complete the merge. It says it can't be done "without further action." It would be helpful to know specifically what action to take instead of having to play detective every time.
I actually opened a case about this last week and still have not heard back. Hoping we can get some feedback soon.
The ability to merge past candidate records with a current candidate (same person) would greatly benefit us as well! Vote for this!