This topic provides information about the rules for each of the columns on each of the worksheets in the import file.
Note: Except in the case of mandatory columns, if no data is provided for a column or there is an error in the data supplied in a column, the default will be used wherever possible.
Baseline Types
- You must provide a value for Type. If this column is empty or populated with unrecognizable data, the row will be ignored. If this column is missing, the sheet will be ignored.
- When importing, if matching data is found in the database, the row is used to update the row in the database. Matching is not case sensitive.
Codes: Activity Codes (global, project, and EPS), Project Codes, and Resource Codes
- You must provide a value for Code Name and Code Value Name. If the row represents a code value, you must also provide a value for Parent Code Name. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- When importing, if matching data is found in the database for Code Name or Code Value Name the row is used to update that code or value. If no matching Code or Code Value is found, the row is used to add a new code or value. The Code Value Name is case sensitive.
- The Type must contain either Code or CodeValue. If the Type is CodeValue, the Parent Code Name column must contain the Name of the code for which this row is a value.
- If the Color column is populated, the values must match the name of the color as shown in the application. To see the name of the color in the application, double click the color column on any activity code in the Enterprise Data page and hover over the color.
- Cells which contain attributes which are represented with options in the application can include either true or false, or 1 or 0.
- The code hierarchy is represented using the Parent Code Name and Parent Code Value Name columns. If the row represents a code value at the top level of the activity code, the Parent Code Name column must contain the name of the parent code as it appears in column A. If the row represents a code value that is not at the top level of the activity code hierarchy, the Parent Code Value Name column must also contain the name of the code value under which the data item will be imported.
Codes: Issue Codes
- You must provide a value for Name and Type. If the row represents a code value, you must also provide a value for Parent Code Name. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- When importing, if matching data is found in the database for Name the row is used to update that code or value. If no matching Code or Code Value is found, the row is used to add a new code or value. The Code Value Name is case sensitive.
- The Type must contain either Code or CodeValue. If the Type is CodeValue, the Parent Code Name column must contain the Name of the code for which this row is a value.
- The Secure column can contain either true or false, or 1 or 0.
- The code hierarchy is represented using the Parent Code Name column. If the row represents a code value at the top level of the issue code hierarchy, the Parent Code Name column must contain the name of the parent code as it appears in column A. If the row represents a code value that is not at the top level of the issue code hierarchy, the Parent Code Value Name column must also contain the name of the code value under which the data item will be imported.
Codes: Overhead Codes
- You must provide a value for Name and Description. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- When importing, if matching data is found in the database for Name the row is used to update that code. If no matching code is found, the row is used to add a new code.
Cost Accounts
- You must provide a value for Id and Name. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- When importing, if matching data is found in the database for both Id and Name the row is used to update the other columns in the database. If matching data is found in the Id and Parent Cost Account columns, but not the Name column, the row is used to update the Name column. If no matching ID or Name value is found, the row is used to add a new cost account.
- The cost account hierarchy is represented using the Root Cost Account and Parent Cost Account columns. If the row represents a cost account at the top level of the hierarchy, the Root Cost Account column must be blank. If the row represents a cost account that is not at the top level of the cost account hierarchy, the Root Cost Account row must contain the Id of the cost account under which the data item is to be imported. Optionally, if the row represents a cost account that is not at the top level of the cost account hierarchy, the Parent Cost Account column can contain the Id of the cost account under which the data item is to be imported.
Currencies
- You must provide a value for Id, Name and Currency Symbol. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- When importing, if matching data is found in the database for both Id and Name the row is used to update the other columns in the database.
- The currency symbol can be one, two, or three characters and must not contain digits.
- The decimal symbol and digit grouping symbol can both be either a period or comma. You cannot use the same symbol for both the decimal and digit grouping symbols.
- The exchange rate specifies the rate between the base currency in the database and the currency being imported or updated. The base currency value is multiplied by the exchange rate to calculate the values displayed in cost fields.
Document Categories
- You must provide a value for Name. If this column is empty or populated with unrecognizable data, the row will be ignored. If this column is missing, the sheet will be ignored.
- When importing, if matching data is found in the database for Name, the row is used to update that category. If no matching code is found, the row is used to add a new category. Matching is not case sensitive.
Document Status
- You must provide a value for Name. If this column is empty or populated with unrecognizable data, the row will be ignored. If this column is missing, the sheet will be ignored.
- When importing, if matching data is found in the database for Name, the row is used to update that status. If no matching code is found, the row is used to add a new status. Matching is not case sensitive.
Financial Period Calendars
- When importing from Excel, you can only create new financial periods.
- You must provide a value for Name, Start Date, and Finish Date. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- The start date must be one day later than the finish date of the latest defined financial period in the database. Financial periods must be at least 7 days long and must not overlap.
- You cannot update or replace the assignment of a financial period calendar to a project by importing using the Update Existing option.
- Financial periods for a financial period calendar must be contiguous, meaning that there must not be a gap between financial periods.
- The Start Date and Finish Date columns must be configured to use a numeric date format in the Excel import sheet. Dates provided in text format are not recognized.
Funding Sources
- You must provide a value for Name. If this column is empty or populated with unrecognizable data, the row will be ignored. If this column is missing, the sheet will be ignored.
- When importing, if matching data is found in the database for Name the row is used to update the other columns in the database. If no matching Name value is found, the row is used to add a new funding source.
- The funding source hierarchy is represented using the Parent Funding Source column. If the row represents a funding source that is not at the top level of the funding source hierarchy, the Parent Funding Source column must contain the Name of the funding source under which the data item is to be imported.
- You can move a funding source to a different parent on import by entering the Name of the new parent in the Parent Funding Source column.
Locations
- You must provide a value for Name, Latitude, and Longitude. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- When importing, if matching data is found in the database for both Name the row is used to update the other columns in the database.
- The Country column must contain the name of a country as it appears in the database. To see a list of the countries that appear in the database, view the Country list in the Add Location dialog box in P6.
- The Latitude column must contain data in the range of "-90" to "90" or "90S" to "90N".
- The Longitude column must contain data in the range of "-180" to "180" or "180W" to "180E".
- The Name field can accept up to 255 alphanumeric characters or symbols. The Street and Street 2 fields can accept up to 200 alphanumeric characters. The Postal Code field can accept up to 20 alphanumeric characters.
Notebook Topics
- You must provide data for Topic Name, as well as the value "True" or "1" for at least one of the following columns: EPS, Project, WBS, or Activity.
- When importing, if matching data is found in the database for Topic Name the row is used to update the other columns in the database.
- The Topic Name field can accept up to 40 alphanumeric characters or symbols.
- The EPS, Project, WBS, and Activity fields can accept values of "True" and "False" or "1" and "0". Null values are considered to be False or 0. The EPS, Project, WBS, and Activity fields cannot be changed to false after a notebook item of the selected type has been assigned at that level.
Risk Categories
- You must provide a value for Name. If the row represents a category that is not at the root level of the hierarchy, you must also provide a value for Parent Risk Category. If the Name column is empty or populated with unrecognizable data, the row will be ignored. If the Name column is missing, the sheet will be ignored.
- When importing, if matching data is found in the database for Name, the row is used to update that category. If no matching Name is found, the row is used to add a new category. Matching is not case sensitive.
- The hierarchy is represented using the Parent Risk Category column. If the row represents a category at the top level of the hierarchy, the Parent Risk Category column must contain the name of the parent category.
Resource Curves
- You can import and update only global resource curves. You cannot update default resource curves.
- You must provide a value for Name. If the Name column is empty or populated with unrecognizable data, the row will be ignored. If the Name column is missing, the sheet will be ignored.
- The Duration % columns can accept numeric values and the percent symbol only.
- The import and update processes do not verify that the total of all the Duration % columns equal 100%.
Step Templates
- You must provide a value for Template Name,.Step Name, and Type. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- When importing, if matching data is found in the database for Template Name,.Step Name, Type, and Parent Step Template Name the row is used to update the other columns in the database. If no matching Template Name,.Step Name, Type, and Parent Step Template Name values are found, the row is used to add a new step template.
- You cannot import data to the Step Count column.
- Weight can be between 0 and 999,999.
- Type can be either Step Template or Step.
- The step hierarchy is represented using the Parent Step Template Name column. If the row represents a step, the Parent Step Template Name column must contain the Name of the step template under which the data item is to be imported.
Timesheet Periods
- You can only create new timesheet periods by importing from Excel.
- You must provide a value for Start Date and Finish Date. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- Timesheet periods must not overlap, but need not be contiguous.
- The Start Date and Finish Date columns must be configured to use a numeric date format in the Excel import sheet. Dates provided in text format are not recognized.
Units of Measure
- You must provide a value for Unit Abbreviation and Unit Name. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- When importing, if matching data is found in the database for Unit Abbreviation or Unit Name the row is used to update the other column in the database. If no matching Unit Abbreviation or Unit Name values are found, the row is used to add a unit of measure. Matching is not case sensitive.
User Defined Fields (Activity, Assignment, Resource, WBS, Risk, Expense, Step, Issue, Document)
- You must provide a value for User Defined Field and Data Type. If these columns are empty or populated with unrecognizable data, the row will be ignored. If these columns are missing, the sheet will be ignored.
- The User Defined Field is limited to a maximum of 40 alphanumeric characters (including special characters).
- When importing, matching is determined by the data in the User Defined Field column. If matching data is found in the database for User Defined Field the row is used to update that UDF, otherwise the row is used to add a new UDF. Matching is not case sensitive.
- If no data, or unrecognizable data, is provided in the Data Type column, the UDF is imported with the data type of Text.
- The data type for a UDF cannot be changed once data has been entered for that UDF anywhere in the application.
- The Data Type column must contain one of these values: text, start date, finish date, cost, number, integer, or indicator. The data type is not case sensitive.
WBS Categories
- You must provide a value for Category. If this column is empty or populated with unrecognizable data, the row will be ignored. If this column is missing, the sheet will be ignored.
- When importing, if matching data is found in the database for Category the row is used to update the other columns in the database. If no matching Category value is found, the row is used to add a new WBS category.