Cost Plan creation through XOG IN - Transaction Classes with Comma produce an error

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Product: Clarity PPM
Keywords: Cost Plan; XOG; Transaction Class; Comma

Steps to Reproduce:

1. Navigate to Administration -> Finance -> Setup
2. Click on "Transaction Classes" under "Classifications"
3. Click on New and create a transaction class with the following details

Transaction Class = 0959,50
Description = 0959,50
Short Description = 0959,50
Transaction Type = Labor

4. Use the following XML to create a Cost Plan (Through XOG IN). Note that transaction class is being set to a value with comma in it. This uses the demo data on a project with ID PR1005. Change the project ID if using a different data set

<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_costPlan.xsd">
 <Header action="write" externalSource="NIKU" objectType="costPlan" version="15.9.1.60"/>
 <CostPlans>
  <CostPlan benefitPlanCode="" code="plan3" finishPeriod="2020-12" investmentCode="PR1005" investmentType="project" isPlanOfRecord="false" name="Plan 3" periodType="MONTHLY" revision="1" startPeriod="2020-01">
   <Description/>
   <GroupingAttributes>
    <GroupingAttribute>transaction_class_id</GroupingAttribute>
   </GroupingAttributes>
   <Details>
    <Detail>
     <Cost>
      <segment finish="2020-01-31T00:00:00" start="2020-01-01T00:00:00" value="99999.0"/>
      <segment finish="2020-02-29T00:00:00" start="2020-02-01T00:00:00" value="12345.0"/>
      <segment finish="2020-03-31T00:00:00" start="2020-03-01T00:00:00" value="12345.0"/>
      <segment finish="2020-04-30T00:00:00" start="2020-04-01T00:00:00" value="12345.0"/>
      <segment finish="2020-05-31T00:00:00" start="2020-05-01T00:00:00" value="12345.0"/>
      <segment finish="2020-06-30T00:00:00" start="2020-06-01T00:00:00" value="12345.0"/>
      <segment finish="2020-07-31T00:00:00" start="2020-07-01T00:00:00" value="12345.0"/>
      <segment finish="2020-08-31T00:00:00" start="2020-08-01T00:00:00" value="12345.0"/>
      <segment finish="2020-09-30T00:00:00" start="2020-09-01T00:00:00" value="12345.0"/>
      <segment finish="2020-10-31T00:00:00" start="2020-10-01T00:00:00" value="12345.0"/>
      <segment finish="2020-11-30T00:00:00" start="2020-11-01T00:00:00" value="12345.0"/>
      <segment finish="2020-12-31T00:00:00" start="2020-12-01T00:00:00" value="12345.0"/>
     </Cost>
     <Units/>
     <Revenue/>
     <GroupingAttributes>
      <GroupingAttribute code="transaction_class_id" value="0959,50"/>
     </GroupingAttributes>
     <CustomInformation>
      <ColumnValue name="partition_code">partition10</ColumnValue>
     </CustomInformation>
    </Detail>
   </Details>
  </CostPlan>
 </CostPlans>
</NikuDataBus>

Expected Results: Cost Plan gets created in the mentioned project

Actual Results: XOG IN fails with the following error message. However, the same Transaction Class can be selected from the UI to create a Cost Plan.

<ErrorInformation>
  <Severity>ERROR</Severity>
  <Description>Missing or invalid value for Grouping Attribute.</Description>
</ErrorInformation>

Environment

Version: 15.9.0

Cause

Due to a defect with ID DE58993.

Resolution

The defect is fixed in version 15.9.2.