• State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 12 replies
  • Subscribers 7 subscribers
  • Views 6169 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

Can not update existing data after changing CDT org.hibernate.ObjectDeletedException

manisht

Hi,

I have a complex CDT structures in the Processes. Earlier i was able to save retrieve and update the data. i made few changes to the CDT and now save a nd retrieve works but I cant update an existing data. I get an exception on "Write to DataStore Node".

I have verified in the process models all pvs and sub-process mappings refer to the latest cdts. I was succesfull in saving the Processes and publishing them eliminating the chances of missing some previous references to the CDT(I think).

The alert and server logs dont specify much but say some deleted object will be recreated.

Here is what i get in the alerts
"There is a problem with task “Write to Data Store Entity” in the process “ Initiate Request”. An error occurred while trying to write to the entity “CK_Request_ET” [id=b886d2c3-19ad-49c2-996a-dccaf4845d09@59999, type=Request (id=12412)] (data store: CK_DATA_STORE). Details: org.hibernate.ObjectDeletedException: deleted object would ...

OriginalPostID-128485

OriginalPostID-128485

  Discussion posts and replies are publicly visible

Parents
  • 0
    Hi Eduardo,
    Last time we were able to resolve it by recreating the CDTs and mapping it again.

    now it is working in the dev env but when we tried an import to QA env the DB functionality broke again. last time(after remapping of new CDTs) we did an import to the QA and it worked for this env also.

    Now, it is throwing exceptions for constraint violation for choices table(Id, not null).
    We are having multiple choices(text) inside Question and trying to fetch and persist data through parent object request itself.

    We have 4 levels of nesting between Request and choices.(Request->KYA Details->Categories->Questions->choices)
    Is the level of nesting the reason for this constraint violation?

    Also I dont understand why this constraint is being violated. If an id is not there appian should autogenerate it and insert the values as it does in the first time when we persist the values. It only breaks at the time of an update. Then also its not consistent across the environments
Reply
  • 0
    Hi Eduardo,
    Last time we were able to resolve it by recreating the CDTs and mapping it again.

    now it is working in the dev env but when we tried an import to QA env the DB functionality broke again. last time(after remapping of new CDTs) we did an import to the QA and it worked for this env also.

    Now, it is throwing exceptions for constraint violation for choices table(Id, not null).
    We are having multiple choices(text) inside Question and trying to fetch and persist data through parent object request itself.

    We have 4 levels of nesting between Request and choices.(Request->KYA Details->Categories->Questions->choices)
    Is the level of nesting the reason for this constraint violation?

    Also I dont understand why this constraint is being violated. If an id is not there appian should autogenerate it and insert the values as it does in the first time when we persist the values. It only breaks at the time of an update. Then also its not consistent across the environments
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.