AnsweredAssumed Answered

Foreign key value in destination table is nullified when origin feature is deleted from relationship - workaround?

Question asked by mmooreWPC on Feb 13, 2019
Latest reply on Jul 19, 2019 by rozekc_washtenaw

I have an SDE geodatabase in which I have an origin feature class with relationship classes to several destination feature classes and tables. When a feature is deleted from the origin table, the foreign keys in the all of the destination feature classes and tables are nullified. This has been annoying for the destination feature classes because the foreign keys have to be reestablished, however, it has resulted in lost data for the destination tables because we have no way to figure out which feature they originally belonged to (because there are no spatial data attached) and this has created serious issues.


Is there a workaround for this or a different setting that I need to consider when setting up my relationship classes?