This example demonstrates how the import actions and the Delete option affect the import of relationships that are linked to activities in external projects.
Update Existing: Update Existing is the default action for the Relationships to External Projects data type. This option looks for matches between the external relationships in the XER file (the export file) and the database. If a match is found, the relationship (e.g., lag value) is updated in the database. If a match is not found, the external relationship from the XER file is added to the database.
Keep Existing: This option looks for matches between the external relationships in the XER file and the database. If a match is found, no changes are made to the external relationship in the database. If a match is not found, the external relationship from the XER file is added to the database.
Do Not Import: This option ignores external relationships in the XER file.
Insert New: This option acts the same as Keep Existing unless the Activities data type import action is set to Insert New. When both Relationships to External Projects and Activities are set to Insert New, the external relationships for the new activities in the database mirror the external relationships in the XER file.
Delete: This option looks for matches between the external relationships in the XER file and the database. If an external relationship is found in the database that does not exist in the XER file, the relationship is removed from the database.
Notes
- When connected to a P6 Professional database: Activity Relationships" privilege to add external relationships to the project. If the user is assigned the "Add/Edit/Delete Activities Except Relationships" privilege, the relationships are not imported.
When connected to a P6 EPPM database: The user must be assigned the appropriate project privilege as defined in P6 to add external relationships to the project.
- Import ignores the external relationship if the external project/external activity was deleted from the enterprise/database.