It is possible to XOG in a user with a Resource ID with more than 32 characters, even though this is limited in Clarity to 32 or less.
When this user is read in other areas of the product (e.g.: a Project 'Project Manager', Resource...), then the XOG write operation will fail with an error like:
[Error] :1:1: attribute "managerResourceID" has a bad value: the length of the value is XX, but the required maximum is 32.
Invalid attribute in input document. Please remove all instances of attribute from document elements and try again.
[Element : Project, Attribute : managerResourceID ].
[Error] :1:1: attribute "resourceId" has a bad value: the length of the value is XX, but the required maximum is 32.
Invalid attribute in input document. Please remove all instances of attribute from document elements and try again.
[Element : Resource, Attribute : resourceId ].
Steps to Reproduce:
Expected Results: XOG request fails.
Actual Results: XOG request succeeds. The resource is now showing a Resource ID of more than 32 characters.
Expected Results: XOG request succeeds.
Actual Results: XOG request fails.
(Steps 6-7-8 would be the same when using rsm_resources_read.xml to read the resource).
If after the Resource ID has been set with >32 chars the resource is financially enabled, the Resource ID cannot be changed back to a shorter one.
Release : 16.1.0
DE68092
This issue is fixed in Clarity 16.1.2.
A new validation/restriction has been added in the nikuxog_user.xsd file for resource ID, firstname & lastname attributes to only allow 32 characters.