Import XML Issues In P6 17.12
Last updated on FEBRUARY 20, 2018
Applies to:Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 126.96.36.199 and later
Information in this document applies to any platform.
The expected behavior for P6 17.12 was to allow Project Codes, Activity Codes and UDF assignments to be retained with the ‘Do Not Import’ option selected for Global Data as long these Codes and UDFs exist in the target database.
However here are the new problems in order of highest impact:
- Resource Assignments (both Resources and Roles) are not being imported with the ‘Do Not Import’ option selected for Global Data even if they exist in the target database. This wasn’t a problem in 17.11.
- Project fails to import if the UDF assigned in the source project does not exist in the target database with the ‘Do Not Import’ option selected for Global Data. The import should be ‘stripping’ these UDFs out, not completely failing the project import.
- When a project fails to import, the project is still being created. Below are examples of import errors yet project is still getting created:
o Invalid TypeObjectId in section: '' when importing Activity ''
o Integer: Mismatched UDF data type. ColumnType: 4 ExpectedType: 5
o ResourceObjectId or RoleObjectId must be set when creating ResourceAssignment objects.
o ActualStartDate: Cannot remove Actual Start if resource has actual work
o PlannedDuration" in ResourceAssignment may not be set to less than 0.
o ActivityActual Finish date must be later than Resume date.
There should be no Import XML Issues.
The issue has the following business impact:
Due to this issue, users cannot import xml
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms