The relationship between newly created features is broken when the data is checked in

Last Published: April 25, 2020


** This issue is addressed in ArcGIS 9.0 Service Pack 3 (SP3) **

If a relationship between two newly created features is established in a disconnected editing session, that relationship will be broken when the data is checked in when the following is true: the Relationship Class is Composite, and the Foreign and Primary Keys are user created attributes.


The relationship is broken because the Foreign Key value for the new feature is changed to the ObjectID value assigned to the related feature in the origin feature class when the data is checked in.


** This issue has been addressed in ArcGIS 9.0 Service Pack 3 (SP3)

Click on the link in Related Information below for Service Pack 3, if necessary. **

If the Service Pack is not available to you, the workaround is to use the ObjectID of the Origin feature class as the Primary Key for the relationship class.

    Article ID:000007383

    • ArcMap 9 x

    Get help from ArcGIS experts

    Contact technical support

    Download the Esri Support App

    Go to download options

    Related Information

    Discover more on this topic