ODF-0231 Error When Trying To Add,Update,Delete Attribute From Custom Object

Products

• Clarity PPM SaaS

Issue/Introduction

Errors occur when creating or deleting attributes on a custom object. 

The APP logs show that Custom XOG write of content packages fails.
Application logs show NullPointerException during XOG custom object instance handler execution. 

STEPS TO REPRODUCE:
1. XOG in custom object.
2. Navigate to the custom object created.
3. Attempt to create a new attribute, update, or delete an attribute. 

Expected: The attribute should be updated,created,or deleted accordingly.

Actual: ODF-0231 error message appears.

The APP log shows ERROR:

[http-nio-8080-exec-257] xbl.XOGCustomObjectInstanceHandler (clarity:user:session:XOG::customObjectInstance::write) (905a144d-47e3-45fe-a99a-61c9467d27bc) Exception importing object
java.lang.NullPointerException: Cannot invoke "com.niku.union.odf.object.ODFObject.getAttributes(String[], com.niku.union.odf.context.Context)" because "object_" is null
 
ERROR | 2026-02-06 04:12:13,820 | —
[http-nio-8080-exec-297] niku.xql2 (clarity:user:session:XOG::contentPack::write) (fa96b8ac-3369-486e-aa51-b07a91e7c003) Database Error thrown 
com.niku.union.persistence.PersistenceException:
SQL error code: 0
Error message: ERROR: relation "odf_ca_t_test_mappings" does not exist

Environment

Any

Cause

The failure is caused by an incomplete or failed initial XOG import which left the object in a corrupted or non-existent state in the database, leading to subsequent transaction errors.

 

Resolution

Perform the custom XOG write of the dependencies of the content package first and ensure each XOG run has no errors.
Re-run the XOG write of the content pack.
Attributes can then be created or deleted on the custom object without errors.