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
After a utility network is created and configured, there may be data management tasks that require migration for staging and testing. The utility network dataset supports migration between geodatabases using the core copy and paste data transfer tools in ArcGIS Pro. When you copy a utility network, the state of the network in the source is preserved in output. This means that the status of subnetworks, diagrams, and network topology are maintained in the target geodatabase along with any existing dirty areas.
A utility network dataset and its related feature classes can also be transferred between a file geodatabase and a mobile or enterprise geodatabase for staging and testing with the Utility Network Package Tools or by using the Export XML Workspace Document and Import XML Workspace Document geoprocessing tools. When this option is used, new utility network dataset is created in the target geodatabase.
The Utility Network Package Tools toolbox is the default method to migrate a utility network. This method migrates the schema, properties, related layers, tables, and data of a utility network through an asset package.
Migrate a dataset using an XML workspace document
An XML workspace document can be used to transfer a utility network across geodatabases at the feature dataset level. Options exist to export data or the schema alone. The Schema only option under the Export Options parameter will export the utility network schema along with existing network rules, network diagram templates, and named trace configurations. The default Data option will additionally export the data, associations, and network diagrams.
There are a few key items to be aware of when migrating a utility network using an XML workspace document:
- The utility network version is maintained in the output geodatabase.
- The network topology of the output dataset is disabled.
- All subnetworks are marked as dirty.
- The diagram consistency state of exported network diagrams is set as inconsistent.
- The system diagram flag is removed for any existing subnetwork diagrams.
- You can export an XML workspace document in the .zip file format to create a smaller, more portable file.
It is important to note that the Export XML Workspace Document tool is not recommended for copying large amounts of geodatabase data with the default Data option. Alternatively, you can use the core copy and paste tools in ArcGIS Pro or an XML workspace document to transfer the dataset's schema between geodatabases followed by use of the Append tool.
It is recommended that you enable the network topology, update subnetworks to re-create your subnetwork system diagrams, and update any other diagrams after importing an XML workspace document into a new geodatabase.
Upgrade a utility network dataset
A utility network dataset can be upgraded to take advantage of new functionality by applying schema changes in the information model. The ArcGIS Pro client release version determines whether an upgrade is available.
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.
Keep in mind that not every ArcGIS Pro and ArcGIS Enterprise release introduce schema changes. Upgrading is only required to take advantage of functionality introduced in a new Utility Network Version.
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:
- Save any edits.
- Obtain an exclusive lock and close any active connections, including services.
- Disable the network topology.
When working with an enterprise geodatabase, the following requirements must be met:
The geodatabase version must be 10.8.1.2.6 or later.
- The input for Dataset to upgrade must be from a database connection established as the database utility network owner 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.
It is important to review Utility network compatibility below before upgrading a utility network using ArcGIS Pro 2.6 or earlier to ensure compatibility with your ArcGIS Enterprise release.
After the utility network dataset is upgraded, you can view the Utility Network Version value 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 who 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. You can view this 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, you can update the portal dataset owner for a utility network. If the existing portal utility network owner leaves the organization, you must change the portal owner to another user. This user must 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, you must also 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 version of 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 a single-user deployment. An enterprise deployment of the utility network uses a services-based architecture that is dependent on both the ArcGIS Pro and ArcGIS Enterprise versions to enable new functionality.
Utility Network Version
When a utility network is created or upgraded, the Utility Network Version value is recorded in the General section of the Network Properties tab on the Network Properties dialog box.
Beginning with ArcGIS Pro 2.7, 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 working in a multimachine deployment in which various versions of ArcGIS Enterprise are installed, all of the portal's federated servers are checked to create a utility network version that is compatible with the highest release available.
- When working with a single-user deployment of the utility network, the version of ArcGIS Pro determines the compatible Utility Network Version value.
For example, when using an enterprise geodatabase with ArcGIS Pro 2.8 and ArcGIS Enterprise 10.8.1, a Utility Network Version value of 4 is created or upgraded. When using ArcGIS Pro 2.8 and ArcGIS Enterprise 10.9 or later, a Utility Network Version value of 5 is created or upgraded.
Utility network compatibility
The following table outlines the compatibility of Utility Network Versions with the various releases of ArcGIS Pro and ArcGIS Enterprise.
As geodatabases and client software are designed to work together, it is recommended that you 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.
For example, you could use ArcGIS Pro 2.6 with a Utility Network Version 4 in ArcGIS Enterprise 10.9 or ArcGIS Pro 2.7 with a Utility Network Version 3 in ArcGIS Enterprise 10.8.1.
This also means that earlier client software releases cannot open utility network datasets that participate in newer functionality. For example, you cannot use ArcGIS Enterprise 10.7 to share a Utility Network Version 4 or consume a Utility Network Version 5 using ArcGIS Pro 2.6.
|Utility Network Version||Compatible ArcGIS Pro version||Compatible ArcGIS Enterprise version|
2.4 and later
10.7 and later
2.6 and later
10.8.1 and later
2.7 and later
10.9 and later
3.0 and later
11 and later