Exporting Project to MSP XML From P6 Creates Incomplete XML Content When the Specific Finish Date Mapping Is Applied in the Export Template
(Doc ID 2386562.1)
Last updated on JULY 28, 2020
Applies to:
Primavera P6 Enterprise Project Portfolio Management - Version 15.1.0.0 to 15.2.15.1 [Release 15.1 to 15.2]Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 15.1.0.0 to 15.2.15.1 [Release 15.1 to 15.2]
Primavera P6 Professional Project Management - Version 15.1.0.0 to 15.2.15.0 [Release 15.1 to 15.2]
Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
When exporting any project to MSP XML, with specific Finish Date mapping (Example: any P6 UDF of Date type vs. Microsoft Project Field "Finish2" or "Finish3") on Activities subject area, the export completes successfully but creates an incomplete MSP XML file. The content will resemble the below example:
--------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<!-- Created by Oracle -->
<Project xmlns="http://schemas.microsoft.com/project/2010">
<SaveVersion>14</SaveVersion>
<Name>*Test-Project Export</Name>
......
<OutlineCodes>
</OutlineCodes>
--------------------------------------
EXPECTED BEHAVIOR
Exporting any project to MSP XML completes successfully and creates the correct MSP XML file.
STEPS
The issue can be reproduced at will with the following steps:
1. Log on P6 Web.
2. Export any project to MSP XML. Modify the template and map any P6 UDF of a Date type to the specific Microsoft Project Field "Finish2" or "Finish3".
3. The Export completes successfully but creates an incomplete MSP XML file.
BUSINESS IMPACT
The issue has the following business impact:
Due to this issue, users cannot export a complete and correct MSP XML from P6.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |