Bug
When a relationship class is built between a feature class in one dataset and a featureclass in another dataset and the first dataset is unregistered as versioned, the second dataset also becomes unregistered without warning.
| Bug ID Number | NIM012874 |
|---|---|
| Submitted | November 5, 2007 |
| Last Modified | April 2, 2025 |
| Applies to | No Product Found |
| Version found | 9.2 |
| Status | Will Not Be Addressed |
Additional Information
We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.Workaround
If Unregister as Versioned is called on the relationship class the destination will also be unregistered as versioned. In this workflow Unregister as Versioned command is being executed on a feature dataset with both the origin feature class and the relationship class in it. That means that RegisterAsVersioned(False) will be called on both objects resulting in the destination feature class (in another feature dataset) being unregistered as versioned. It is the user’s responsibility to understand relationships within their data model.Steps to Reproduce
Bug ID: NIM012874
Software:
- No Product Found
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