Project Data tab of the Primavera XML or Primavera XER Template Dialog Box of the Import/Export Project Dialog Box

Overview

Use this tab to select an import action when the same data exists in the import file and project being updated.

Many data items are both created and assigned when you import, typically when they have a one-to-many relationship (for example, risks, project calendars, activity codes). So if you import a new calendar, not only is the calendar object created, but the process of importing will also assign the calendar to whichever objects in the import file are using it. However, some data items are only created on import because their definition includes the information about the data item to which they belong (for example, scheduling options, WBS nodes, and activity relationships). Other data items are only assigned on import, meaning that the item must exist in the database for the import process to assign it to another item (for example, baseline assignments, high level planning assignments).

Select Remove from P6 to delete those values in the database that are not contained in the file you are importing.

Screen Elements

Name field

The type of global or project data for import.

Import Action list

Determines what action to take when importing:

Insert New: Retains the data in the existing project and adds new data even when a matching record exists.

Keep Existing: Retains data in the existing project and does not overwrite it with the updated data or adds new data if the record does not exist and you have the appropriate security privileges.

Update Existing: Overwrites data in the existing project with updated data and adds new data if the record does not exist.

Do Not Import: Retains data in the existing project and does not import the updated data for this data type.

Assign: Assigns the codes and code values during import. This action is available for codes only when importing from a Primavera XML file and for unsecured codes only when importing from an XER file.

Ignore: This action is available for codes only. This action does not assign the codes and code values during import. This applies only to the assignment of codes and code values, not to whether the codes and code values are imported. If you chose to Insert New, Keep Existing, or Update Existing for the code type on the Global Data tab, the code and its values will be imported, even if you choose Ignore here.

Remove from P6 option

Determines whether to remove the selected item from the database if a matching item is not found in the import file. This option is available if the import file is in XML format. This option is not available for secure codes.

Tip

To understand how the import of secure codes is handled, see the P6 EPPMImporting and Exporting Guide.
Project Record Data covers data that is specific to a project, for example notebooks, budget logs, spending plans, and project UDFs. In most cases, multiple instances of these items are not permitted. For example, you cannot have two spending plans assigned to a project. However, it is possible to have multiple budget logs assigned to one project, therefore if you select Insert New as the import action for the Project Data Record duplicate records can be created for budget logs.

Getting Here

Click Projects.
On the Projects navigation bar, click EPS.
Click the Actions menu and select Import/Export Projects.
In the Import/Export Projects dialog box, click the Import tab.
1. Click the Import Type list and select Primavera XER or Primavera XML.
2. Click the File field, click Browse and select a file to import.
3. Click the Manage Templates button.
In the Manage Primavera Templates dialog box, click the name of a template.
In the Primavera Template dialog box, click the Basic tab.
Click the Project Data tab.

Related Topics