Administrator > Upload users > Troubleshoot user upload validation errors

Troubleshoot user upload validation errors

This section describes how to deal with common validation errors in the user upload wizard. After making the suggested changes in a text editor, try to import the new users again through the wizard.

The following table summarizes validation errors that may occur while uploading user data, and provides troubleshooting guidance (angle brackets "<>" are placeholders for the actual values):

User Upload Wizard Validation Error Messages
Validation Error Messages Suggested Action
Data import file version information missing or incorrect. Indicates that the first line (i.e., that is not commented out or blank) of the data file is missing or incorrect. The first line of the file should be similar to the following, where "X.x" represents the correct version number: "Data Upload File Format Version: X.x". Ensure that this is the first uncommented or non-blank line, and that it contains the correct version number.
Column <column_name> does not have a header. Add an appropriate header for the specified column (see the sample template file for guidance).
Header is duplicated in columns <column_name> and <column_name>. Remove one of the specified column headers.

Column header in position <position_number> does not match any company device or any custom field.

Replace the specified column header with an appropriate header (see the sample template file for guidance).
Mandatory column header <column_header> expected in column <column_name>. Add the specified mandatory column header, or replace an existing header with the mandatory header. The following columns are mandatory: Operation, User. If any users are being added or updated, it is also necessary to add First Name, Last Name, and Site. Finally, added users require at least one valid email device.
No column header matches a configured email device. Ensure that at least one column header matches the name of a configured email device.
User <User> is duplicated in an earlier line. Remove one of the rows in which the user value is duplicated.
Line does not contain any email values (at least one email device must be configured for each User). Remove the line, or add an email device for the user in the specified line. (At least one email device must be specified for each new user so that xMatters can send them a message with instructions and a link for setting up their new account.)

Device type is not supported in the User Upload Wizard (only the Email, Voice, Text Phone, and Text Pager Device types are supported).

Remove the unsupported device type or replace it with a supported type.
Line has more values (<number_of_values>) than the number of column headers (<number_of_
headers>).
Indicates there is a mismatch between the number values in a line and the number of column headers for the line. Remove any extra values for the specified line.
Mandatory value is not present in line. Modify the specified username, or remove its line from the user Upload file.
Value exceeds the maximum length of <number> characters. Modify the specified value so that it is within the maximum character limit.
Line has Site value <Site_value> that does not exist in the database. Correct the spelling of the Site name, or replace the specified Site value with a Site that exists in the database.
The email address is invalid. Ensure that the specified email address is properly formatted and does not contain special characters that are not allowed (e.g., #, $, &).
Phone has an invalid number (phone numbers must be in the following format: <area code> <phone number>. Ensure that the specified phone number is properly formatted and does not include extra spaces or dashes. For example, the following are valid: 5555555, 555 5555555.
Number is not valid (only digits and spaces are allowed). Ensure that the specified number includes only digits and spaces.
Submitted ZIP file contains more than one data file. For storage purposes, xMatters creates an archive (ZIP) file for each data import file. However, each archive must include only one data file. If you receive this error, contact your xMatters Administrator.
Could not create the parent folder <folder_name>. xMatters was unable to create a parent folder for the data import file (e.g., due to a server problem, network issue, etc.). If you receive this error, contact your xMatters Administrator.
Could not access import data file <import_data_file_name>.

xMatters was unable to access the data import file (e.g., due to a server problem, network issue, etc.). If you receive this error, contact your xMatters Administrator.

Value is mandatory for this field. Add the mandatory Custom Field value for each user.
Value must be "true", "false", "yes", or "no". Modify the Custom Field value to one of the specified values.
Value does not exist in the list choices. Specify an existing list value for the Custom Field.
Value length must be between <lower_number> and <higher_number>. Modify the length of the Custom Field value to be within the specified range.
Value must be between <lowend> and <highend>. Modify the Custom Field value to be within the specified range.
Value cannot be parsed to an integer. Modify the Custom Field value to an Integer.
Value cannot be parsed to a decimal. Modify the Custom Field value such that there is at least one digit on either side of the decimal point (e.g., 1.2).
Row must have at least an operation (remove or process) followed by a user. Ensure that their is an operation of remove or process specified for this user, as well as the associated user ID.
Operation must be either 'remove' or 'process'. Ensure that their is an operation of remove or process specified for this user.
Row with 'process' operation needs values for the following fields (in order): <field_list> Ensure that the specified rows have valid values.
Cannot find user to remove. You cannot delete the user because they do not exist in the system. This may be due to an incorrect user ID (i.e., a typo), or the user may have been previously removed. Correct the typo or remove the user from the file.
Cannot remove the last Company Admin. You cannot delete the last Company Administrator for a Company. Remove this user from the file.
Cannot remove the last Super Admin. You cannot delete the last Super Administrator from the system. Remove this user from the file.
User Supervisor has not been specified; <currently_logged_in_User> will be used. If a user supervisor is not specified, the currently-logged-in user will be assigned as the user supervisor.
User Supervisor is invalid as it is going to be removed. This is a warning that although the user will be deleted, you should be aware that they are a user supervisor of another user.
User Supervisors are invalid as they are going to be removed: <position_list>. This is a warning that although the users will be deleted, you should be aware that they are user supervisors of another user.
Specified User Supervisor is not a valid User: <position_list>. Specify a valid user as user supervisor.
Specified User Supervisors are not valid: <position_list>. Specify valid users as user supervisors.
User cannot be their own User Supervisor: <position_list>. Specify a valid user supervisor other than the user.
<UserID> is specified as the supervisor for one or more users, but does not have the required permission (ability.act.PersonSupervisor).

Specify a valid user as user supervisor, or assign the specified user the required permission to supervise users.

Import job has more than <number> lines; use 10,000 or fewer lines per job. Break the import job into parts that include 10,000 or fewer lines.