Bug
False conflict is generated for the related records when the editing is done through a versioned view.
| Bug ID Number | BUG-000131226 |
|---|---|
| Submitted | May 28, 2020 |
| Last Modified | December 13, 2024 |
| Applies to | ArcSDE/Enterprise Geodatabase |
| Version found | N/A |
| Operating System | Windows OS |
| Operating System Version | N/A |
| Status | Will Not Be Addressed |
Additional Information
Editing feature classes through a versioned view in the geodatabase functionality such a relationship class is an unsupported workflow. This is documented at the link below: What type of data can be edited using SQL https://desktop.arcgis.com/en/arcmap/10.4/manage-data/using-sql-with-gdbs/what-type-of-data-can-be-edited-using-sql.htm To add more context, editing feature classes through a versioned view in relationship classes does not maintain referential integrity. For example, using ArcGIS Desktop or ArcGIS Pro, the foreign key in the destination object is set to null when it's origin object is deleted, editing through the versioned view does not. Therefore, unexpected behavior is seen while generating conflicts.Workaround
The issue is not reproducible when the primary key field and foreign key field of the relationship class are set in two different fields.
Steps to Reproduce
Bug ID: BUG-000131226
Software:
- ArcSDE/Enterprise Geodatabase
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App