Custom object corrupt after XOG insert
search cancel

Custom object corrupt after XOG insert

book

Article ID: 281210

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

After using XOG to insert an object, the newly created object is corrupt and throws "No Object Found" message in Clarity PPM UI

Resolution

You may not be able to safely delete this object due to impacts, as there are many impacted tables with possible orphans.

Our recommendation is to go with either of the below recommendations: 

  1. Perform a new refresh on this environment if this is a lower environment.
    • Note this will remove any new work you are currently working on so this will have to be backed up

or

  1. Remove the access permissions to this object from all the users.
    • This will make it not visible in UI.
    • Eventually when you refresh the environment the object will be gone (only applies to lower environments)
    • After updating the user permissions, go ahead and create the object you need again, with a different ID, manually. See if this works.
    • If this works, add the attributes you need / update by XOG and test