Import Data Messages

As you are importing data, the Results window will report back information as the import process progresses, including information about which part of the import process is occuring and information about which part of the import process may have gone wrong. Before you click the Finish button and complete the data import process, you should review the messages and attempt to address any issues noted in the spreadsheet, and then re-import the data. You cannot import data when errors are present.

In the table below, brackets {} are used as placeholders for variables that you may see in the error messages. For example, the message Row {row} was skipped because the following columns had invalid values: {value}. could appear in the Results pane like this: Row 2 was skipped because the following columns had invalid values: C.

The following error messages may be returned during data import:

Error Message	Description
Exception when the server attempted to open {filename}.	This is a general error message. If you continue to get this error message, re-download the template and try again. If the error persists, please call Serena support.
Could not open server copy of the workbook file {filename}. The file does not exist or this user does not have access.	Make sure that you are opening the template and that you have the appropriate permissions to import data. Only users with the Import Data (View/Edit) permission will be allowed to import investment and resource data. Users must also have permission to add resources (Create Resource), add investments (Create Project Investments), add resource teams (Create New Resource Team), and add resource roles (Create Resource Role).
Row {row} was skipped because the following columns had invalid values: {value}.	Verify the information in the row and column indicated. Ensure that the columns have valid values and re-import the data.
There was an unexpected error processing file. {filename}	This is a general error message. If you continue to get this error message, re-download the template and try again. If the error persists, please call Serena support.
A worksheet with the name of {worksheet tab name} was already processed.	The names of the tabs in the template should not be modified. New tabs should not be added. Verify that only four tabs exist (Investments, Resource Roles, Resource Teams, and Resources) in the copy of the template you are using to import data.
The worksheet with the name of {worksheet tab name} did not have all the required columns.	Each tab in the template has required columns: Investments tab: Import, Investment, and Investment Type. Resource Roles tab: Import, Role Name, Rate, and Rate Effective. Resource Teams tab: Import and Team. Resources tab: Import, User Name, Primary Resource Role, and Email.
There was an error opening the Microsoft Excel file. The file may be corrupt or of the wrong format.	Verify that you have attempted to import data using a copy of the template. If you continue to get this error, re-download the template.
The user does not have sufficient permissions to create {name of resource, investment, resource team, or resource role}.	Only users with the Import Data (View/Edit) permission will be allowed to import investment and resource data. Users must also have permission to add resources (Create Resource), add investments (Create Project Investments), add resource teams (Create New Resource Team), and add resource roles (Create Resource Role).
Row {row} was skipped because the following values created a duplicate key {value}.	Verify the information in the row and column indicated. Duplicate user names, investment names, resource role names, and resource team names will not be imported.
Row {row}, Column {column} contained resource type {invalid resource type} which is invalid.	Verify the information in the row and column indicated. There are three valid resource types: Contractor, Permanent, and Part Time.
Row {row}, Column {column} contained role name {duplicate role name} which is already in the system.	Verify the information in the row and column indicated. Duplicate resource role names are not allowed.
Row {row}, Column {column} contained investment type {invalid investment type} which is either not an investment, not in the system, or is not creatable.	Verify the information in the row and column indicated. The investment type is incorrect. It may be misspelled, it may not exist, or it may not be a valid child investment of the parent investment.
Row {row}, Column {column} contained resource team {invalid resource team} which is not in the system.	Verify the information in the row and column indicated. The list of resource teams currently available can be found in the Resources module.
Column {column} was ignored because it was a duplicate.	An attribute can have only one value.
Row {row}, Column {column} contained user name {duplicate user name} which is already in the system.	Verify the information in the row and column indicated. Duplicate user names are not allowed.
Column {column} was ignored because they attribute key specified was not valid for importing.	Verify that the correct system name for the attribute is being used. The system name of an attribute can be found on the Attributes tab in the Custom Attributes view of the Configuration module.
Row {row}, Column {column} contained list value {invalid list value} which is invalid.	Verify the information in the row and column indicated. List values associated with attribute lists can be found on the Lists tab in the Custom Attributes view of the Configuration module.
Row {row} was skipped because it contained parent {invalid parent} which is not in the system or in the spreadsheet.	Verify the information in the row and column indicated. If you are importing a parent, be sure that it's a valid parent for the resource team or investment.
Row {row}, Column {column} contained resource role {invalid resource role} which is not in the system.	Verify the information in the row and column indicated. Resources can only be assigned to an existing resource role. Verify that you are importing the resource with the correct resource role name. If that role is not present, add it, and then re-import the resource.
There was an error assigning license to user {user name}. User was imported with no license.	A license could not be assigned to the user. Verify that the license is the correct license or that your organization has enough licenses.
Row {row} was skipped because parent investment type cannot contain this investment type.	Verify the information in the row indicated. Investment information can only have a child that is valid for the investment type being imported. Valid children can be found in the Containment tab on the Investment Types tab in the Types Setup view in the Configuration module.
Row {row} was skipped because parent had same name as self.	Parent-child relationships for resources, resource teams, and investments must have the correct parent-child relationships: Resource information must conform to the hierarchy defined in the Resource Breakdown Structure Investment information can only have a parent that is valid for the investment type being imported. Valid parents can be found in the Containment tab on the Investment Types tab in the Types Setup view in the Configuration module.
The parser detected a recursion error. Please check the parent-child relationships of your {parent of resource team name or parent of investment name}. All processing will be stopped and nothing was imported!	See the previous entry.
Row {row}, Column {column} contained value {invalid attriubute type value} which is not valid for the attibute type.	Verify the information in the row and column indicated. When importing attribute data, the value must be an appropriate value for the attribute's data type. If it is a list value, it must be one of the list values associated with that attribute type.
Errors occured during processing file or there were no valid rows for importing.	Verify that you have selected an template, that there is data in at least one tab in the template, and that the Import column is set to True.
Row {row}, Column {column} contained user name {invalid email address} which is not a valid email address.	Verify the information in the row and column indicated. An email address must be the full email address. For example: rforster@serena.com.
Row {row}, Column {column} contained security group {security group name} which is not in the system.	The user was not imported. Verify the information in the row and column indicated, and then re-import the user. The list of security groups available can be found in the Administration module, Users and Security view, on the Groups tab. The name of the security group in the should identical to the name of the security group shown in the Name field.
There was an error assigning user {row} to security group {column}. User was imported with no security group.	The user was imported, but without an associated security group. Verify the name of the security group and that it is the name of a valid security group. The list of security groups available can be found in the Administration module, Users and Security view, on the Groups tab. The name of the security group in the should identical to the name of the security group shown in the Name field.
Row {row} was skipped because it contained a ParentAgileWorkItem {name of parent agile work item} which is not in ths system or in the spreadsheet.	Verify the information in the row and column indicated. A parent agile work item must exist in order for an agile work item to be associated to it.
Row {row}, Column {column} contained AgileWorkItem {name of agile work item} which is either not an AgileWorkItem, not in the system, or is not creatable.	Verify the information in the row and column indicated. Valid agile work item types that are already in the system (and that can be imported) can be found in the Attributes tab on the Work Types tab in the Data Model Setup view of the Configuration module.
Row {row} was skipped because a Product had same name as self.	Verify the information in the row and column indicated. Owning investment names must be unique. Verify the name of the owning investments in the template and re-import the data.
Row {row} was skipped because it contained a Product {name of owning investment} which is not in the system or in the spreadsheet.	Verify the information in the row and column indicated. Ensure that the owning investment name is in the system or in the spreadsheet.
Row {row} was skipped because the work hierarchy was not found.	Verify the information in the row indicated. Ensure that a work hierarchy is available for the agile work item you are trying to import.
Row {row} was skipped because the AgileWorkItemType cannot exist without a parent under the work hierarchy.	Verify the information in the row indicated. Ensure that the agile work item you are trying to import has a parent that exists in the work hierarchy. The parent is defined in the ParentAgileWorkItem column.
Row {row} was skipped because the AgileWorkItemType of the parent is not supported by the work hierarchy.	Verify the information in the row indicated. Verify that the agile work item's parent work item type exists in the existing work hierarchy.
Row {row} was skipped because the AgileWorkItemType is not a valid type under its parent AgileWorkItemType.	Verify the information in the row indicated. Verify that the agile work item's parent work item type is a valid parent based on the existing work hierarchy.
Moved {row} from parent {row} to parent {row}.	Verify the information in the rows indicated. Ensure that the agile work item's new parent is the one you want it to be.

The following status messages may be returned during data import:

Status Message	Description
Finished parsing of worksheet named {worksheet tab name}.	The validation process for data import has finished.
The following rows were parsed successfully: {row}.	Status message. Each row that was parsed successfully will be listed. For example, The following rows were parsed successfully: 2, 3, 4, 5, 9.
Starting parse of worksheet named {worksheet tab name}.	Status message.
User {user name} already had a license. No action was taken.	Status message.
The import job has finished.	Status message.
The import job has started.	Status message.
Finished assigning licenses.	Status message.
Attempting to assign license named {license name} to users.	Status message. Indicates the license type being assigned to users during import.
License was assigned to user {user name}.	Status message. Each user that was successfully assigned a license will be listed. For example: License was assigned to user gmclennan, rforster, lbalcom.