Bug ID Number |
BUG-000165850 |
Submitted | March 11, 2024 |
Last Modified | June 5, 2024 |
Applies to | ArcGIS Pro |
Version found | 3.2.1 |
Operating System | Windows OS |
Operating System Version | 10.0 64 Bit |
Status | As Designed
After review by the development team, it has been determined that this behavior is as designed. See the Additional Information section for details.
|
Additional Information
This is not supported and is being marked as designed. When opening project 'x' and then, from that project, calling a script that opens project 'x' again via its path, it is the equivalent of opening the same project a second time. The second instance is read-only. This is reproducible in the UI without Python. Open project x, then open it again. The second instance title reads 'Project X [Read Only]'.
In the second instance, try adding a field and saving the changes. The same "Cannot get exclusive schema lock" error is returned. This may have worked in an earlier release of ArcGIS Pro, but around the 2.9 release, the application introduced the read-only lock. Arcpy.mp was extended to provide an isReadOnly property on the ArcGISProject object to enable confirming if a project can be saved.
The following note is in the ArcGISProject class help topic.
Note:
Projects can be referenced multiple times, but only the first reference can be saved directly because the other references will be opened as read-only. The ArcGISProject object has an isReadOnly property that can be used to determine a project's read state before calling a method such as saveACopy instead of save.
Workaround
Declare a variable by hard coding the path to the feature class rather than using arcpy.mp to access the feature class.
Steps to Reproduce