Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
After uploading employee data to Microsoft Viva Glint, you might receive error or warning messages. Errors or warnings can occur at the file level or the line level.
- File level: File level issues relate to data across all records in your file or the file itself.
- Line level: Line level issues relate to rows of data in your file. The message might provide line numbers to indicate where the issue exists or it might describe conditions where you can find affected rows.
- Warnings: Warnings are informational and might require your attention to determine whether corrections are necessary. These records are uploaded to Viva Glint but don't pass validation or might not function as expected because of invalid data.
- Errors: Errors are issues that prevent data from being uploaded to Viva Glint. A file-level error prevents the entire file from being uploaded, and a line-level error prevents only specific lines from being uploaded.
Use the following table to:
- Determine whether data issues are warnings or errors
- Determine whether a file or line of data is impacted
- Find links to resolution steps
Upload type | Error or warning | File or line level | Message - shortened | Resolution |
---|---|---|---|---|
Employee data | Error | File | DERIVATION_ERROR: File is in an unexpected format... | How to resolve |
Employee data | Error | File | DERIVATION_ERROR: Processing the file failed. Derivation failed due to invalid data... | How to resolve |
Employee data | Error | File | DERIVATION_ERROR: The date format is incorrectly configured... | How to resolve |
Employee data | Error | File | DUPLICATE_COLUMN: Column <Attribute Name> appears two times... |
How to resolve |
Employee data | Error | File | ENRICHMENT_FAILURE: Attribute column headers in the uploaded file do not match your Glint import configuration... | How to resolve |
Employee data | Error | File | ENRICHMENT_FAILURE: Row <100> length doesn't match header's length... |
How to resolve |
Employee data | Error | File | MANAGER HIERARCHY ERROR: Manager Email address user@contoso.com is mentioned more than once... |
How to resolve |
Employee data | Error | File | MANAGER_HIERARCHY_UPDATE_ERROR: There should be at least one employee record with no manager... | How to resolve |
Employee data | Error | File | MISSING_COLUMN: Missing required column <Attribute Name> ... |
How to resolve |
Employee data | Error | Line | DUPLICATED_EMAIL (Deleted user): The Email Address <user@contoso.com> in the user file is already assigned to a different user... |
How to resolve |
Employee data | Error | Line | DUPLICATED_EMAIL: The Email Address <user@contoso.com> in the user file is already assigned to a different user... |
How to resolve |
Employee data | Error | Line | DUPLICATED_EXTERNAL_USER_ID: The Employee ID <x> in the user file is already assigned to another employee... |
How to resolve |
Employee data | Error | Line | FIELD_TOO_BIG_FATAL: Required field <Attribute Name> can't be longer than 64 characters. |
How to resolve |
Employee data | Error | Line | INVALID_EMPLOYEE_DATA: Email <user@contoso.com> OR external user id <x> is assigned to multiple users... |
How to resolve |
Employee data | Error | Line | INVALID_EMPLOYEE_DATA: Skipping line number <x> because column <y> contains unsupported characters. |
How to resolve |
Employee data | Error | Line | INVALID_STATUS: Status value LEAVE is invalid... |
How to resolve |
Employee data | Error | Line | MISSING_REQUIRED_VALUE: Line <x> is missing a required value... |
How to resolve |
Employee data | Error | Line | RECORD_STAGING_FAILURE: Found <x> existing record that has been previously deleted corresponding to line number <y> . |
How to resolve |
Employee data | Error | Line | UNEXPECTED_ATTRIBUTE: The following attribute/attributes <Attribute Name> are in the file but not configured in Viva Glint... |
How to resolve |
Employee data | Warning | Line | CHAR_LIMIT_EXCEED_NON_MANDATORY: Non-Required field <Attribute Name> is longer than 64 characters... |
How to resolve |
Employee data | Warning | Line | INVALID_EMAIL: There are <number> employees without a valid Work Email... |
How to resolve |
Employee data | Warning | Line | INVALID_LOCALE: Line <x> the Locale value <locale> is not a valid locale string. |
How to resolve |
Employee data | Warning | Line | INVALID_PERSONAL_EMAIL: Line <x> the Personal Email value <email address> is not formatted like a valid email address. |
How to resolve |
Employee data | Warning | Line | INVALID_USER_TIMEZONE: Line <x> the User Timezone value <timezone> is not a valid international timezone string. |
How to resolve |
Employee data | Warning | Line | MANAGER_HIERARCHY_UPDATE_WARNING: external user id <x> is mapped to manager reference <y> which is not on file or system... |
How to resolve |
Employee data | Warning | Line | MANAGER_HIERARCHY_UPDATE_WARNING: There are <number> employee records without a manager... |
How to resolve |
Employee data | Warning | Line | SUSPICIOUS_VALUE: Value of Employee <Attribute Name> for Employee ID <ID> contains suspicious characters... |
How to resolve |
ID update | Error | File | CONFIGURATION_ERROR: All Employee Ids match the existing values for all users... | How to resolve |
ID update | Error | File | CONFIGURATION_ERROR: This file has a missing Employee Id at line <x> ... |
How to resolve |
ID update | Error | File | CONFIGURATION_ERROR: This file must contain the First Name, Last Name, Email Address, and New Employee ID... | How to resolve |
ID update | Error | File | DUPLICATE_ID: The Employee ID <ID value> on line <y> is already associated with user@contoso.com ... |
How to resolve |
ID update | Error | File | DUPLICATE_IN_FILE: Lines <x> and <y> contain the same Employee ID of <z> ... |
How to resolve |
ID update | Error | File | MISSING_COLUMN: Missing mandatory column <attribute name> ... |
How to resolve |
ID update | Error | File | NO_EMPLOYEE_RECORD: Line <x> with email user@contoso.com does not correspond to any existing user in Viva Glint... |
How to resolve |
ID update | Error | File | UNEXPECTED_ATTRIBUTE: The following attribute/attributes <attribute name 1> , <attribute name 2> are in file but not configured in Glint... |
How to resolve |
ID update | Warning | Line | SUSPICIOUS_VALUE: Warning at line <x> : The First Name (or Last Name) of <y> does not match the stored value of <z> . |
How to resolve |