XOG Import fails with “Could not find match for teamMember with teamUid” for wrong value for cop_phase attribute

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

On importing XOG with baseline and resources and Status report, an error is thrown that refers to teamUid and baselines. The issue is due to wrong value for cop_phase Status Report attribute

 

STEPS TO REPRODUCE:

1. In Clarity Classic, create a new project
2. In Project Summary pick a Stage value
3. Create two tasks and set up one as Phase by opening in Gantt and indenting it
4. Assign a resource and baseline the project
5. Add a new Status Report on it
6. For Current Phase, pick a value
7. Note the value will be the same as the task you set as Phase in step 3
8. Now export the project via XOG
9. Open the XOG file. Note the value for cop_phase is numeric:
   • <ColumnValue name="cop_phase">5010000</ColumnValue>
10. This corresponds to the PRID.PRTASK for the task we created in step 3
11. Modify the value to something else (not a Phase in the system), i.e:
    • <ColumnValue name="cop_phase">5022000</ColumnValue>
12. Change the project code in the file to a new project code that is not yet in the system
13. XOG the project in as a new project

Expected Results: The XOG to succeed with a warning that value for Phase was incorrect.

Actual Results: XOG import fails with a completely irrelevant error message:

        <Severity>FATAL</Severity>

        <Description>Project Object insert failed</Description>

        <Exception><![CDATA[

java.lang.Exception: Could not find match for teamMember with teamUid = testuser for

                              BaseLinesDetails for resource = .

Environment

Clarity 16.3.1

Cause

DE168984

Resolution

Working as designed if internal cop_phase ID does not match an existing value in Clarity

Workaround: clear the cop_phase value for the attribute and XOG the project in