introduction
When managing person knowledge in Adobe Studying Supervisor (ALM), chances are you’ll encounter errors throughout a CSV add. There are two frequent error messages you might even see:
- Duplicate Entries – This error signifies {that a} person with the required e-mail deal with seems a number of occasions within the CSV file.
- Duplicate Customers – This error implies that a person with the required e-mail deal with already exists within the system.
Understanding these errors and figuring out how one can resolve them is crucial to sustaining a clear and correct person database. On this weblog put up, we’ll discover the causes of those errors and present you how one can resolve them.
Understanding duplicate entry errors
Error message:
Duplicate entry – Entry in subject ‘-email’
Trigger:
This error happens if the identical e-mail deal with seems a number of occasions within the CSV file. ALM requires that every e-mail deal with within the file be distinctive to keep away from creating a number of entries for a similar person.
Answer:
To resolve this error, you want to be sure that every e-mail deal with seems solely as soon as in your CSV file. To take action:
- Examine the CSV file: Open the CSV file and search for duplicate e-mail addresses.
- Take away Duplicates: If duplicates are discovered, consolidate the person knowledge into one entry per e-mail deal with.
- Validate a CSV file: Use the CSV validation software offered by Adobe (https://cpcontents.adobe.com/public/beta/csv-validator/index.html) to verify for any remaining points. Go away the corporate identify as “Root,” map the columns in your CSV to the fields proven within the validator, and click on Validate.
When you appropriate the duplicate entries, the file ought to import efficiently.
Understanding the Duplicate Person Error
Error message:
Duplicate Customers <電子メール アドレス> already exists within the system.
Trigger:
This error happens when a person with the required e-mail deal with already exists within the ALM system, which regularly occurs when person knowledge comes from a number of techniques, reminiscent of an HR system or an worker administration resolution.
Answer:
To resolve this error, be certain that the UUID (person distinctive identifier) of the person in your CSV matches the UUID in ALM. Here is how:
- Examine for present person profiles: Discover the UUID of an present person profile in ALM.
- Replace UUID: If the UUID within the CSV doesn’t match with the UUID in ALM, manually replace the UUID of the learner’s outdated profile by the ALM UI.
- Use constant UUIDs: Guarantee new UUIDs are imported by way of CSV to any extent further.
Instance state of affairs:
In case you are sourcing knowledge from ADP (HR system) or a workforce administration resolution, when a contract employee converts to a everlasting worker, a brand new profile could also be created in ADP, leading to two profiles for a similar person with the identical e-mail deal with however completely different UUIDs.
To merge these accounts in ALM:
- Manually replace an outdated profile: In ALM, manually replace the UUID of the outdated profile to match the brand new profile.
- Future Imports: Be sure that future CSV uploads use the brand new UUID.
