Utility network dataset administration

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.

Note:

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.

When working with an enterprise geodatabase, the version of ArcGIS Pro and ArcGIS Enterprise determines the Utility Network Version of the utility network dataset that is created or upgraded. To learn more, see Utility network compatibility.

Tip:

The version and upgrade history for a utility network 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 3 to Utility Network Version 5, all schema changes for versions 4 and 5 are included. Some utility network versions require additional steps to be followed after the upgrade process. Review steps for each version included in the upgrade path.

For more information, refer to the specific version in the Utility network upgrade history.

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.
  • For utility networks that are version 3 and earlier, the dataset must be registered as versioned.

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.

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.

Learn more about how to manage content

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.

Functionality is dependent on the ArcGIS Pro client version when working with a utility network using the single-user model. Utility networks that are stored in an enterprise geodatabase use a services-based architecture. This multiuser model deployment is dependent on both the ArcGIS Pro and ArcGIS Enterprise versions to enable new functionality.

The version of ArcGIS Pro and ArcGIS Enterprise determines the Utility Network Version value when creating or upgrading a utility network:

  • When using an enterprise geodatabase, the version of ArcGIS Pro and the portal's federated server are used to determine the compatible Utility Network Version value.
  • When using a file geodatabase, the version of ArcGIS Pro determines the compatible Utility Network Version value.

For example, when using an enterprise geodatabase with ArcGIS Pro 2.7 and ArcGIS Enterprise 10.8.1, a Utility Network Version 4 is created or upgraded. When using ArcGIS Pro 2.7 and ArcGIS Enterprise 10.9 or later, a Utility Network Version 5 is created or upgraded.

Learn more about client and geodatabase compatibility

Utility Network Version

When a utility network is created or upgraded, the Utility Network Version is recorded in the network properties in the General section.

Utility Network properties

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.
This also means that earlier client software releases cannot open utility network datasets that participate in newer functionality. For example, ArcGIS Enterprise 10.6 cannot be used for sharing a utility network that has a Utility Network Version 2.

Utility network compatibility

The following table outlines the ArcGIS platform compatibility for a utility network:

  • ArcGIS Pro release—The ArcGIS Pro version used to create or upgrade the utility network.
  • Utility Network Version—The version of a utility network dataset.
  • ArcGIS Enterprise release—The version of ArcGIS Enterprise base deployment. Applies only to utility networks created in the multiuser model.

Utility Network VersionArcGIS Pro releaseArcGIS Enterprise release

1

2.1.x

10.6 and later

2

2.2.x

10.6.1 and later

2

2.3.x

10.6.1 and later

3

2.4.x

10.7 and later

3

2.5.x

10.7 and later

4

2.6.x

10.8.1 and later

5

2.7.x

10.9 and later

ArcGIS platform compatibility for a utility network