Unable to delete org data due to decision_concept dangling entry

[himeshr]

Describe the bug
Unable to delete org data due to decision_concept dangling entry.
Test for deletion of metadata for apftestach org in Staging environment.

Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on table "form" violates foreign key constraint "decision_concept_form" on table "decision_concept"
  Detail: Key is still referenced from table "decision_concept".
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2270)
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1998)
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:570)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:420)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:366)
        at sun.reflect.GeneratedMethodAccessor409.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114)
        at com.sun.proxy.$Proxy121.executeUpdate(Unknown Source)
        at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:175)
        ... 149 common frames omitted

q2024-08-21 11:21:23.761  INFO 1675484 --- [http-nio-8021-exec-50] o.a.s.f.security.AuthenticationFilter    : DELETE /implementation/delete?deleteMetadata=true Status: 409 User: AchalaB@apftestach Organisation: apftestach Time: 12773 ms

[himeshr]

Bug missed out while working on avniproject/avni-webapp#787, in-case the form is in the targeted org, but the decision concept is in say parent org (openchs-1).

Could not find code version that matches this stack trace, so seems weird we encountered this in staging.

ErrorStackTrace.txt

[himeshr]

Unable to test this on staging after the fix, due to memory issues limit on the staging machine.
@AchalaBelokar Test the card in prerelease during 10.0 release testing.