Available with Standard or Advanced license.
After a utility network is created and configured in a geodatabase, additional administration tasks are necessary, depending on your organizational needs. Dataset administration tasks for a utility network can include the need to migrate the dataset between geodatabases, upgrade, or update the portal utility network owner. It is also important to be aware of the supported compatibility between ArcGIS clients and geodatabase datasets, such as a utility network.
Migrate a utility network dataset
Once a utility network is created and configured, there are data management tasks that may require migration. Migration of a utility network dataset and its related feature classes may be needed to transfer data between enterprise geodatabases or to stage a test environment. The Utility Network Package Tools toolbox can be used to migrate a utility network. An asset package can be created from an established utility network and applied against a staged utility network created in another geodatabase. Asset packages support cross-database platform use. To import data into a utility network, the core Append tool can be used.
The utility network dataset does not currently support migration between geodatabases using core data transfer tools such as copy in ArcGIS Pro.
Upgrade a utility network
A utility network dataset must be upgraded to take advantage of new functionality by applying schema changes in the information model. The ArcGIS Pro client release version determines if an upgrade is necessary.
The version of ArcGIS Pro determines the Utility Network Version of the utility network dataset that is created. The ArcGIS Pro version determines if the utility network dataset requires an upgrade. Refer to the table below to view the ArcGIS Pro release version and corresponding Utility Network Version:
|ArcGIS Pro release||Utility Network Version|
The Utility Network Version can be viewed in the General section of the Network Properties tab.
Upgrades are cumulative between versions and include changes from skipped versions. For example, if you update the utility network from Utility Network Version 2 to Utility Network Version 4, all schema changes for versions 3 and 4 are included. The upgrade history is listed in the Upgraded property found in the General section of the Network Properties tab.
To upgrade a utility network dataset, use the Upgrade Dataset tool. Before the upgrade is attempted, however, the following requirements must be met:
- The geodatabase must be upgraded to the latest version.
- An exclusive lock must be obtained; any active connections must be closed, including services.
- The network topology must be disabled.
- Any edits must be saved.
When working with an enterprise geodatabase, the following requirements must be met:
- The input for the Dataset to upgrade must be from a database connection established as the database utility network owner.
- The input for the Dataset to upgrade must be from a database connection with the versioning type set as branch.
- The connected portal account must be the portal utility network owner.
The following steps are necessary after you upgrade to Utility Network Version 4:
- Register the feature dataset that contains the utility network as branch versioned to version the new junction and edge objects. To learn more, see Register a dataset as branch versioned.
- Enable the network topology.
- Republish any existing services with an updated map that includes the nonspatial junction and edge object tables.
- Reconcile all named versions to regenerate dirty areas based on schema changes made during upgrade.
After the utility network dataset is upgraded, the Utility Network Version can be viewed in the General section of the Network Properties tab. To review specific schema changes for each release, see Utility network upgrade history.
Update the portal utility network owner
When working with an enterprise geodatabase, a utility network dataset has two owners that are used to control access for administrative tasks. In addition to the database user that creates a utility network, the active portal user account is recorded as the portal utility network owner. When a utility network is created, these owners are determined based on the user accounts for the database connection and active ArcGIS Enterprise portal.
- The database utility network owner is recorded as part of the fully qualified name of the utility network dataset.
- The portal utility network owner is stored as metadata for a utility network. This can be viewed using the network properties when accessed using a database connection as the data owner.
While the data owner (database user) cannot be updated without re-creating the data, the portal dataset owner can be updated for a utility network. If the existing portal utility network owner leaves the organization, it is necessary to change the portal owner to another user. This user should comply with the same user type and privilege as the original owner. Refer to the Update Portal Dataset Owner tool for more information.
After the portal owner is updated for the dataset, it is also necessary to change item ownership for any existing portal items for map, image, and feature layers.
ArcGIS platform compatibility
As an administrator, it is important to be aware of the compatibility between ArcGIS clients, the geodatabase, and the utility network dataset when working with mixed releases. Utility networks that follow the multiuser model use a services-based architecture and are dependent on both the ArcGIS Pro and ArcGIS Enterprise client versions to enable new functionality.
Functionality is dependent on the ArcGIS Pro client version when working with a utility network using the single-user model.
Utility Network Version
When a utility network is created, the version of ArcGIS Pro is recorded in the network properties in the General section for the Created with ArcGIS Pro Release property. The Utility Network Version value is determined by the version of ArcGIS Pro used to create or upgrade a utility network dataset.
As geodatabases and client software are designed to work together, it is recommended to keep these versions in sync when possible. As a general rule for working with mixed releases, ArcGIS client applications (such as ArcGIS Pro and ArcGIS Enterprise) are backward compatible when working with the utility network:
- Later versions of ArcGIS Enterprise can share earlier versions of the utility network.
- Later versions of ArcGIS Pro can be used to view and edit earlier versions of the utility network.
The following table outlines the ArcGIS platform compatibility for a utility network:
- ArcGIS Pro release—The version used to create or upgrade a utility network. This determines the Utility Network Version value.
- Utility Network Version—The version of a utility network dataset.
- ArcGIS Enterprise release—The version of ArcGIS Enterprise to which the utility network can be shared. Applies only to utility networks created in the multiuser model.
|Utility Network Version||ArcGIS Pro release||ArcGIS Enterprise release|
10.6 and later
10.6.1 and later
10.6.1 and later
10.7 and later
10.7 and later
10.8.1 and later