Provide a list of information that is not retained when merging duplicate users

I contacted support and there is no list of either the information that is retained or the information that is lost when merging duplicate user records. This makes it difficult to know what information needs to be manually moved to the original user account before merging. With the lack of functionality of the merge duplicates function (there are many other ideas addressing these issues) it seems like this would be a necessary document.

  • Amy Hentschke
  • Mar 20 2024
K-12 Core / User Management
  • Attach files
  • Jeanne Townsend commented
    20 Mar 15:02

    Amen! It is so difficult to merge records when you don't have clarity on what data is retained from the merge. I often put the records side-by-side and go through all possible fields to make sure I'm not missing anything, which negates the benefit of the merge feature.

    It would also be incredibly helpful to be able to choose which record should be the 'master' record rather than being forced to keep the older record and delete the newer record.

    If you are reading this comment, and have opinions about the Core > Potential Duplicate Users (i.e. Merge) Function, check out--and vote for--these other good ideas.


    THE MORE WE VOTE, THE BETTER OUR CHANCES OF SEEING CHANGES MADE!


    • K12CO-I-3037 - When merging duplicates, please let us select which user to keep

    • K12CO-I-740 - Merge Duplicates select which information is kept

    • K12CO-I-2507 - I would like for merged duplicate records to have a history

    • K12CO-I-115 - Merge Users Option (outside of Potential Duplicates area)

    • K12CO-I-592 - Potential Duplicate Users task

    • K12CO-I-1557 - When merging profiles under POTENTIAL DUPLICATES on the CORE dashboard, need option to select which username and password to preserve

    • K12CO-I-3502 - Flag duplicate files as potential duplicates so they can be easily merged

    ×

    Attachments Open full size

Related ideas