Utility Network Data Schema Version

[EsraCındır]

When I compare sample Utility Network data schemas in ArcGIS Pro, I noticed that version 3.2 includes some additional supporting tables like D_rename, whereas these kinds of tables are missing in the 3.3 model.

Will it cause any issues if I use these older tables, such as D_rename from version 3.2, with the 3.3 data model?

Also, are these Utility Network versions tied to specific versions of ArcGIS Pro or ArcGIS Enterprise? If I upgrade my Enterprise version later on, could it potentially break or cause issues with a Utility Network that was created using an older version?

[AyanPalit]

@EsraCındır There is definite Utility network compatibility to ArcGIS Pro and ArcGIS Enterprise.

As a general rule for working with mixed releases and the utility network, ArcGIS client applications (such as ArcGIS Pro and ArcGIS Enterprise) are backward compatible. However, best practice is to align with the Network Management Release Plan

The Utility Network schema changes are tied to functionality and documented at the Utility Network Foundation solution release notes. You can review Water Utility Network Foundation Release notes

[PatrickGCowan · Accepted solution]

Regarding the D_ tables, yes, it is possible to use older D_ tables with a newer schema. A word of caution though. The newer schema is likely different from the older schema, and the configuration and rename may not give you the results you are expecting because of this difference. You can and should do an update of these tables and review them for changes in the schema.

The suggested workflow would be as follows:

• Add the older D_ tables to the newer asset package
• Run the Create Rename Table tool in the Utility Network Package Tools toolbox.
  • Specify only the asset package parameter. Do not enter anything in the rename fields. This will update the rename table against the new schema while retaining any previously set values.
• Run the Create Configurations Table tool in the Utility Network Package Tools toolbox.
  • Specify only the asset package parameter. Do not enter anything in the configurations fields. This will update the configuration table against the new schema while retaining any previously set values.
• Review the updated D_ tables and make changes as you see fit.
• Use the Config and/or Rename tables when applying the asset package.