BUG-000137415 for ArcSDE/Enterprise Geodatabase

Bug ID Number	BUG-000137415
Submitted	February 11, 2021
Last Modified	June 5, 2024
Applies to	ArcSDE/Enterprise Geodatabase
Version found	10.7.1
Operating System	Windows OS
Operating System Version	N/A
Status	Will Not Be Addressed

Additional Information

The behavior comes down to a data modeling problem. The problem is there are "chained" relationships based on the same field being both foreign and primary keys. Although the geodatabase may allow certain edits to these types of relationships, geodatabase replication is more strict. Where there is a dangling foreign key, nullify it. One reason for this is to avoid the dangling records being inadvertently related to a different record if at a later point in time an original record is created with that key value. The recommendation is for "chained" relationships to be based on different key fields for each relationship class (do not have the same field used for all the relationships). If the relationships cannot be changed accordingly, then update the data to ensure values for all the related records in the chain before the sync. The particular feature class, in this case, had 7 relationships – 5 with origin keys and 2 with foreign keys (one foreign key based in the field being edited and the other was based on another field – the latter is the recommended way to establish these relationships).