Clarity: XOG OBS write for unit update is behaving like an insert rather than an update in 12.0.6

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Description:

Details:

OBS XOG will throw an error (XOG-2628: OBS Unit Name must be unique within an OBS</Description>) when you attempt to update an existing OBS unit to another unit.

Steps to Recreate:

1. Create a test OBS using the following XML:

   <?xml version="1.0" encoding="UTF-8"?>    
   <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_obs.xsd">   <Header action="write" externalSource="NIKU" objectType="obs" version="8.0.0.4088"/>  <obsTypes>    <obs code="NOV_DALLAS_OBS" isSecurity="true" name="Novell Dallas Test OBS">      <level depth="1" name="Level1"/>        <level depth="2" name="Level2"/>          <level depth="3" name="Level3"/>          <unit code="OBS_DALLAS_1" name="Dallas Test 1">          <unit code="OBS_DALLAS_2" name="Dallas Test 2">         <unit code="OBS_DALLAS_3" name="Dallas Test 3"/>      </unit>   </unit>   </obs> </obsTypes></NikuDataBus>

2. Navigate to UI and observer that the OBS exists and is as written.
   
   
3. Attempt to move a unit to be the child of another unit by using the following XML:

   <?xml version="1.0" encoding="UTF-8"?> <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"   xsi:noNamespaceSchemaLocation="../xsd/nikuxog_obs.xsd">  <Header action="write" externalSource="NIKU" objectType="obs" version="8.0.0.4088"/>    <obsTypes>       <obs code="NOV_DALLAS_OBS" isSecurity="true" name="Novell Dallas Test OBS">        <level depth="1" name="Level1"/>         <level depth="2" name="Level2"/>          <level depth="3" name="Level3"/>        <unit code="OBS_DALLAS_1" name="Dallas Test 1">      <unit code="OBS_DALLAS_2" name="Dallas Test 2"/>    <unit code="OBS_DALLAS_3" name="Dallas Test 3"/>     </unit>   </obs> </obsTypes></NikuDataBus>

4. You'll get the following error: XOG-2628: OBS Unit Name must be unique within an OBS</Description>.

Expected Results: XOG error is thrown and OBS updates cannot be made.

Actual Results: Move OBS units manually.

Solution:

Workaround:

Manually make OBS unit changes in UI rather than XOG.

Status/Resolution:

This issue has been determined to be due to a new defect introduced in 12.0.6 and is logged as CLRT-54278.

Keywords: OBS, XOG, update unit, CLRT54278.

Environment

Release:
Component: STUDIO