Alternative for Circular relationship of a custom object with Incident Object
SummaryFeature deprecated by Oracle after 19A to create circular realtionship.
We were using a workflow using a custom object that was created in relationship with the incident object in a passion where we were adding and editing the record for that custom object while editing an incident and saving both at the same time and the incident got saved successfully with that custom record.
It was a circular relationship like incident and custom object were having both child and parent relationship with each other. This type of relationship is not supported by OSvC after19B upgrade and recently we upgraded our site from 19A to 20D. So, as this feature is not supported we are facing issues in continuing with our previous workflow. We are unable to save the incident record with a custom object record, it throws an error "A valid rv_ref chain cannot be created. Loop detected". Oracle gave a workaround in which the user should save the incident first with all the fields and