An exception occurred while trying to update an object instance odf_blueprint
search cancel

An exception occurred while trying to update an object instance odf_blueprint

book

Article ID: 408807

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

After adding the MySubobject sub-object module into a blueprint, we receive the following error:

An exception occurred while trying to update an object instance odf_blueprint

Even after removing the subobject from the blueprint, it continues erroring out.

The app-ca.log file shows the following traces:

ERROR 2025-08-27 17:28:36,044 [http-nio-8080-exec-3] ppm.rest (clarity:myuser:6009308__5:PPM_REST_API) (27cd0224-443e-43fc-947b-fa7a89e25da0) 
com.ca.ppm.rest.exception.NotFoundException: API-1003 : Could not find resource MySubobject.
 
ERROR 2025-08-27 16:46:36,478 [Event Interest Registration Thread] odf.ObjectController (clarity:myuser:-1:bpm.startup.interestRegistration) () Error occurred trying to materialize object "z_mysubobject"
com.niku.union.odf.exception.ODFException: Error resolving derived attribute "z_attribute1". There is no attribute with code "z_attribute1" defined for object "inv".
 at com.niku.odf.object.ODFObjectImpl.resolveDerivedAttributes(ODFObjectImpl.java:863)
 at com.niku.odf.object.ODFAbstractObjectImpl.<init>(ODFAbstractObjectImpl.java:372)
 
ERROR 2025-08-27 16:46:37,097 [Event Interest Registration Thread] odf.ObjectController (clarity:myuser:-1:bpm.startup.interestRegistration) () Error occurred trying to materialize object "z_mysubobject"
com.niku.union.odf.exception.ODFException: Error resolving derived attribute "z_attribute2". There is no attribute with code "z_attribute2" defined for object "inv".

 

 

Environment

All supported Clarity releases

Cause

The MySubobject object contains two virtual attributes referenced on the Investment (inv) object, but those are orphan as the Investment object fields have been deleted

Resolution

Please proceed as follows:

  • Administration > Studio > Objects > Locate the Investment object
  • Look for the virtual fields referenced on the log: z_attribute1 and z_attribute2
  • You will notice these are missing
  • Create two attributes with the IDs referenced on the log
  • Administration > Studio > Objects > MySubobject  object
  • Open the object and go to the attributes tab
  • Remove the orphan z_attribute1 and z_attribute2 attributes
  • Administration > Studio > Objects > Investment object
  • Remove the z_attribute1 and z_attribute2 attributes we created
  • The blueprint is now fully functional again