Value for resourceid tag in cmn_users_write.xml is case sensitive
search cancel

Value for resourceid tag in cmn_users_write.xml is case sensitive

book

Article ID: 218883

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

We notice that the resourceid tag in cmn_users_write.xml is case sensitive. A sample XML is as below.

<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_user.xsd">
 <Header action="write" externalSource="NIKU" objectType="user" version="15.9.2.910"/>
 <Users>
  <User externalId="sample007" isLDAP="true" oldUserName="******" uiThemeDefaultPartitionCode=" " userLanguage="Norwegian" userLocale="no_NO" userName="sample007" userStatus="LOCK" userTimezone="Europe/Amsterdam" userType="INTERNAL" userUid="sample007">
   <PersonalInformation emailAddress="[email protected]" firstName="Sample" lastName="007"/>
   <Resource resourceId="SAMPLE007"/>                          
  </User>
 </Users>
</NikuDataBus>

If the Resource ID of the User being manipulated through this XML is in lower case - sample007, and if the upper case letters are used in the XML, then the following error is thrown.

java.lang.Exception: Resource SAMPLE007 already associated with another user. Please use an unique resourceId

Cause

This is an expected behaviour of the cmn_users_write.xml template

Resolution

Extract the exact Resource ID from the system (with all the case information) and use in cmn_users_write.xml.

Additional Information

Following point is of relevance with respect to the Resource IDs.

  • Resource IDs are not case sensitive when creating a new Resource. That is if "sample007" is stored against unique_name column of the srm_resources table, then a new resource cannot be created with ID "SAMPLE007".