Project 'associatedParent' incorrectly set when using XOG

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

When we XOG-OUT a project (A) with a parent set and a project (B) without a parent set at the same time, the ”associatedParent” of project (B) is set, even though it should be blank.

STEPS TO REPRODUCE
1. Login to Clarity and navigate to Projects (Classic)
2. Create Project A 
3. Set the PARENT attribute of Project A to A01
4. Create Project B and make sure PARENT is empty
5. XOGOUT both the projects using below

<?xml version="1.0" encoding="UTF-8"?>
<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd">
  <Header version="6.0.11" action="read" objectType="project" externalSource="NIKU">
  <args ...>
  </Header>
  <Query>
      <Filter name="projectID" criteria="OR">ProjectA,ProjectB</Filter>
  </Query>
</NikuDataBus>

Expected: The XOGOUT XML should have Project B with a blank Parent.

Actual: Project B's parent is set as A01 which is the parent of Project A. 

<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_project.xsd">
<Header action="write" externalSource="NIKU" objectType="project" version="16.3.1.1473"/>
<Projects>
        <Project projectID="ProjectA" associatedParent="ProjectA0" .... >
        <Project projectID="ProjectB" associatedParent="ProjectA0" .... >
      </Projects>
      <XOGOutput>
</NikuDataBus>

Workaround: Remove the associatedParent from Project B XML when xogging back in. 

Resolution

DE169074 - Fixed in 16.3.3