Bug ID Number |
BUG-000178567 |
Submitted | August 8, 2025 |
Last Modified | August 27, 2025 |
Applies to | ArcGIS Pro |
Version found | 3.3.6 |
Operating System | Windows OS |
Operating System Version | 11.0 64 bit |
Status | Known Limit
After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. The issue's Additional Information section may contain further explanation.
|
Additional Information
This happens after upgrading 10.9.x or earlier geodatabase in SQL Server. After this upgrade operation, the fully qualified names of tables and feature classes no longer contain the database name in the SQL geodatabase while the diagram layer, diagram rule and layout definitions still reference this database name.
Workaround
In this SQL geodatabase example, any <FeatureClassName> network source class is referenced in the diagram definitions as 'Elec_UN.UNOWNER.<FeatureClassName>' while it should be referenced as 'UNOWNER.<FeatureClassName>'.
The workaround consists in removing the database name in the diagram definitions like detailed below.
Note: This workflow applies configuration and administration tools that must be run using a database connection to the utility network in the enterprise SQL geodatabase.
The following are requirements:
- Create a database connection to the database using the database utility network owner credentials.
- Connect to ArcGIS Enterprise portal using the portal utility network owner credentials.
- Run the 'Export Diagram Template Definition' tool to export both the Rule and Layout Definition (A_BuilderDef.ndbd output file) and the Diagram Layer Definition (A_LayerDef.ndld output file) for diagram template A.
- Update the layer definition for template A.
- Rename the A_LayerDef.ndld file with the .zip extension => A_LayerDef.zip, and unzip A_LayerDef.zip.
- Open the unzipped resulting Dummy.json using a text editor such as Notepad.
- Search for the '<DatabaseName>.' strings; for example 'Elec_UN'. In this example, and replace all these string occurrences by an empty string''.
- Save the Dummy.json file and close it.
- Zip the edited Dummy.json file and rename the zip file with the .ndld extension as 'A_LayerDef.ndld'.
- Delete Dummy.json file.
- Update rule and layout definition for template A.
- Rename the A_BuilderDef.ndbd file with the .zip extension => A_BuilderDef.zip, and unzip A_BuilderDef.zip.
- Open the unzipped resulting Dummy.json using a text editor such as Notepad.
- Search for the '<DatabaseName>.' string; for example, 'Elec_UN'. In this example, and replace all these string occurrences by an empty string ''.
- Save the Dummy.json file and close it.
- Zip the edited Dummy.json file and rename the zip file with the .ndbd extension as 'A_BuilderDef.ndbd'.
- Delete Dummy.json file.
- Update the template definitions.
- Run the 'Import Diagram Template Definition' tool to import both the edited Rule and Layout Definition (A_BuilderDef.ndbd edited file) and Diagram Layer Definition (A_LayerDef.ndld edited file) for diagram template A.
- Stop and restart the related network service.
- Create a diagram based on template A and verify it now opens as expected without drawing error anymore.
- Repeat steps 1 to 4 for each diagram template B, C, D, and so on, existing for the utility network.
Steps to Reproduce