Unable to create a new Resource via XOG with a partition other than 'System'
search cancel

Unable to create a new Resource via XOG with a partition other than 'System'

book

Article ID: 278953

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

XOG fails when creating (or updating) a new resource with a partition other than 'System' over XOG.

Steps to Reproduce:

  1. For the Resource object, assign a Partition Model. Ensure that the resource to be updated.
  2. In the Classic UX Resource List, add the partition column.
  3. Change the partition for a given Resource that is not Financially Enabled to any other than 'System' (e.g.: 'IT').
  4. XOG out the resource.
  5. Modify the attributes needed to create a new user, such as 'resourceId', 'username'.
  6. XOG in this new resource.

Expected Results: A new resource with the new partition ('IT') is created.

Actual Results: XOG fails with the following error:

<ErrorInformation>
  <Severity>FATAL</Severity>
  <Description>This record has not been inserted</Description>
  <Exception><![CDATA[
com.niku.union.utility.MessageKeyException: Location, Department, Resource and Transaction class are required to financially enable a Labor Resource.
    at com.ca.clarity.financial.setup.services.resource.ResourceFinancialsBaseService.validateResourceFinancials(ResourceFinancialsBaseService.java:257)
    at com.ca.clarity.financial.setup.services.resource.ResourceFinancialsBaseService.validate(ResourceFinancialsBaseService.java:158)
    [...]]]>
  </Exception>
</ErrorInformation>

The same occurs when updating the partition of a similar resource via XOG.

This XOG fragment can be used to XOG in, when using the PMO Accelerator Sample Data, to create a Resource 'test' after associating the Resource object to the 'Organization' Partition Model:

<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_resource.xsd">
  <Header action="write" externalSource="NIKU" objectType="resource" version="16.2.0.2112" />
  <Resources>
    <Resource employmentType="EMPLOYEE" externalId=" " includeInDatamart="true" isActive="true" isExternal="false" managerUserName="admin" resourceId="test" resourceType="LABOR" username="test">
      <PersonalInformation displayName="test, test" emailAddress="@" firstName="test" lastName="test" />
      <ManagementInformation availability="8" openForTimeEntry="false" trackMode="None" userFlag1="false" userFlag2="false" userNumber1="0" userNumber2="0" />
      <CustomInformation>
        <ColumnValue name="partition_code">partition10</ColumnValue>
        <ColumnValue name="obj_anonymize_pii">false</ColumnValue>
      </CustomInformation>
      <General addedBy="admin" addedDate="2024-02-06" />
      <OBSAssocs complete="false" />
      <SkillAssocs />
      <Calendar baseCalendar="Standard" resetCalendar="false" />
    </Resource>
  </Resources>
</NikuDataBus>

Environment

Clarity 16.2.0.

Cause

DE79616

Resolution

This issue has been fixed in Clarity 16.2.2.