Error Messages When Employee Parsing and Importing Stop

The following characters are not allowed: []<>\"&!

Any input value has invalid characters such as []<>\"&!

Parsing stops with this exception and no employees are imported.

Failed to upload data from file. Please make sure the content is valid and/or specify number of lines to ignore then try to upload the file again.

Unhandled error happens (in EJB or DB) when setting a value to any of the fields in import like suffix, username etc. or when creating employees. Ex: SQL exception when longer value than field can accept is entered in the file.

Parsing stops with this exception and no employees are imported.

An employee with same name is already assigned to one of the selected Balance Data Source(s).

Duplicate balance data source Third-party systems that provide data to the system, including employee and device states, and data change events. Typical data sources are phone switches, PBXs, or LANs. assignment in file for an employee

Parsing stops with this exception and no employees are imported.

The extension ''{0}'' has already been assigned to employee {1}, {2}."

Duplicate data source extension ID in file for an employee

Parsing stops with this exception and no employees are imported.

The extension ''{0}'' does not exist as a primary extension in data source ''{1}''.

Invalid data source extension in file for an employee

Parsing stops with this exception and no employees are imported.

Error Messages When Employee Parsing Continues but Importing Stops

Record number {0}: Employee {1} {2}: could not be imported to the organization: {0} as the organization does not exist.

Organization given in file for an employee not found

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Record number {0}: Employee {1} {2}: could not be imported to the organization: {0} as you do not have access rights to the organization

User does not have access to organization given in file for an employee

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Record number {0}: Employee {1} {2}: could not be imported as the first name is missing.

Missing first name for an employee

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Record number {0}: Employee {1} {2}: could not be imported as the last name is missing

Missing last name for an employee

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Record number {0}: Employee {1} {2}: could not be imported as {0} is not a valid email

Invalid email address in the file for an employee

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Record number {0}: Employee {1} {2}: could not be imported as there was a problem finding the specified data source: {0}.

Invalid data source ID in the file for an employee or there was an error in EJB or DB when setting the DS information to the employee object

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Record number {0}: Employee {1} {2}: could not be imported as there was a problem finding the specified data source extension: {0}.

Invalid data source extension ID in the file for an employee

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported as the external employee id is duplicate: {0}.

The import contains a duplicate employee ID.

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported as data source extension is duplicate: {0}

The import contains duplicated data source extension data.

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported since both data source extension and employee Id cannot be present at the same time.

You can provide either the data source extension, or the employee ID. You cannot provide both.

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported since no data rows found in the import file.

The import file did not have any data rows.

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported as there are invalid characters in field: {0}.

The import file contained invalid characters such as [] <> \ & !

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported as supervisor: {0} is not a valid supervisor.

The supervisor with the specified name does not exist.

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported as supervisor: {0} is missing Supervisor flag.

The supervisor needs to have the isSupervisor flag set to true.

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported as supervisor: {0} does not belong to employee's organization hierarchy.

The supervisor needs to belong to the employee's organization, or to one of the employee’s organization’s parent organizations.

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported as team lead: {0} is not a valid team lead.

The team lead with the specified name does not exist

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported as team lead: {0} is missing isTeamLead flag.

The team lead needs to have the isTeamLead flag set to true.

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Could not be imported as team lead: {0} does not belong to employee's organization hierarchy.

The team lead needs to belong to the employee organization, or to one of the parent organizations of the employee organization.

Adds the message and continues parsing to find more errors if any. But no employees are imported.

Warning Messages that do not Affect Parsing or Importing

Record number {0}: Employee {1} {2}: Proficiency is set to default value 1.0 as the given value was not valid.

Invalid proficiency value in file for an employee

Continues importing the employee and others in file. This message is only a warning.

Record number {0}: Employee {1} {2}: Quality score is set to default value 0 as the given value was not valid.

Invalid quality score value in file for an employee

Continues with importing the employee and others in file. This message is only a warning.

Messages After Employee Import About User Account Information

Is provided with the default password and will be asked to change it on first login.

Default password is provided.

Information message. Employee is already imported and user information set.

The requested user name: {0} is already in use so user name: {1} is assigned to the employee.

Username modified

When the user name specified in the file is taken, the username is modified to make it unique. The msg provides the new user name.

Record number {0}: Employee {1} {2}: Error(s) encountered while updating user information.

Error occurred in EJB/DB when setting user information

Employees are already created. Error occurred when setting user information.