Error "ODF-0101: No object found" after deleting abstract object custom attributes that have associated sub-object virtual attributes

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Description:

Error appears in Clarity UI after deleting abstract object custom attributes that have associated sub-object attributes

Steps to Reproduce:

1. Create a new sub-object for the Project master object
2. Create a new custom attribute on the Investment object
3. Create a new virtual attribute on the sub-object from step 1
4. Delete the custom attribute on the Investment object

 

Expected Result: Report a runtime error saying "The selected attributes cannot be deleted as they are being used. The error conditions are marked below." with a Cancel button and associated items listed.

Actual Result: Alerted with "Do you want to delete the attribute and items listed below ?" with no items listed, and Yes/No buttons. Clicking on Yes will cause the system to encounter future errors.

Solution:

WORKAROUND:

If the abstract attribute has not yet been attempted to be deleted (no error on sub-object yet), then:

1. Locate all virtual attribute references first, and delete those from objects / sub-objects where present
2. Now delete the abstract attribute

Otherwise if the abstract attribute has attempted to be deleted (and there are errors with the sub-object), then:

1. Recreate the definition for the abstract object attribute in Studio
2. Restart the application services
3. The errors on the sub-object should now be cleared, if not refresh the browser and/or repeat step 2
4. Locate all virtual attribute references first, and delete those from objects / sub-objects where present
5. Now delete the abstract attribute

 

STATUS/RESOLUTION:

Resolved in Clarity 13.3

Environment

Release: ESPCLA99000-13.2-Clarity-Extended Support Plus
Component:

Resolution

Though this issue is resolved and you should not be able to delete an attribute that is being used on a sub object (virtual attribute)  if by chance, you see a warning while trying to delete the attribute, and also have the ability to delete if from the master object, please delete the attribute from the sub object first to avoid any possibility of orphaned derived attributes.