Bug
The creation of a relationship class fails when a participating feature class and table are already added to a map.
| Bug ID Number | BUG-000157690 |
|---|---|
| Submitted | April 20, 2023 |
| Last Modified | September 19, 2024 |
| Applies to | ArcGIS Pro SDK for .NET |
| Version found | 3.1 |
| Operating System | Windows OS |
| Operating System Version | 10.0 64 Bit |
| Status | As Designed |
Additional Information
Creating or deleting a relationship class (as well as other data definition language (DDL) commands) definitely requires an exclusive lock. Changing the schema requires exclusive access and is the reason why those locks exist. Users must stop their web services, change the schema, and then restart their web services- at minimum. It will be safer to republish the data so that the service is made aware of any changes to the schema. The fact that some of the geoprocessing tools and Python allow these changes is the actual bug. These operations must not be allowed unless the exclusive lock can be obtained; it should work the same as the SDK.Workaround
To perform a data definition language (DDL) operation on a feature class, any web service that uses the feature class must be stopped, and other ArcGIS Pro instances using the feature class must be closed. After changing the schema, restart or republish the web services if the schema changes impact the web service.
Steps to Reproduce
Bug ID: BUG-000157690
Software:
- ArcGIS Pro SDK for .NET
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