Is there any way of knowing exactly which objects are causing a Circular Reference Delete Constraint?
Hi, we had this problem a while ago and the solution was to avoid a “cascade delete” delete constraint on 2 different relational attributes in the same object class. Say a case where you have a Company that has many Departments and many Projects. Then you have Orders with a reference to both one Department and one Project. If both reference has cascade delete and the cascade starts on “Company” → both Department and Project → 2 incoming cascades to Order you will get an error like this, without actually having a “circular reference” in your database.
And also i think you can limit your search to the “bottom” of the cascade, if this is the case for you as well.
Maybe this helps 
3 Likes