Bug
Running the ChangeVersionCommand on a FeatureClass that has subtypes defined but no "default" subtype defined causes the FeatureLayer to become disassociated with it's FeatureClass. No error message is given to the user.
| Bug ID Number | NIM035852 |
|---|---|
| Submitted | June 4, 2008 |
| Last Modified | June 5, 2024 |
| Applies to | No Product Found |
| Version found | Other |
| Status | Will Not Be Addressed |
Description
The Change Version command in ArcMap disconnects the Feature Layer from the source Feature Class, when no default subtype has been defined. No error message is produced; the layer is just not associated to any Feature Class.Cause
This problem is due to IFeatureWorkspace.OpenFeatureClass failing when no default subtype is set, and the FeatureClass is already open but pointing to a different version. The change version code is not anticipating the call to fail and is setting the FeatureLayer's FeatureClass to NULL.Workaround
Set a default subtype for the FeatureClass.
Steps to Reproduce
Bug ID: NIM035852
Software:
- No Product Found
Get notified when the status of a bug changes
Related Information
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