Trace network dataset administration

Available with Standard or Advanced license.

After a trace network is created and configured in a geodatabase, additional administration tasks are necessary, depending on your organizational needs. Dataset administration tasks for a trace network can include the need to migrate the dataset between geodatabases, upgrade, or update the portal trace network owner. It is also important to be aware of the supported compatibility between ArcGIS clients and geodatabase datasets for the trace network.

Trace network dataset migration

After a trace network is created and configured, there may be scenarios that require the dataset to be transferred between a file geodatabase and a mobile or enterprise geodatabase for staging and testing. The trace network dataset does not currently support migration between geodatabases using the core copy and paste data transfer tools in ArcGIS Pro; however, other options are available to migrate your trace network data.

You can use an XML workspace document to transfer a trace network across geodatabases at the feature dataset level using the Export XML Workspace Document and Import XML Workspace Document geoprocessing tools. Using these tools, you can export data or export only the schema. The Schema only option of the Export Options parameter exports the trace network schema along with existing network diagram templates and named trace configurations. The default Data option also exports the data and network diagrams.

Keep the following in mind when migrating a trace network using an XML workspace document:

• The trace network version is maintained in the output geodatabase.
• The network topology of the output dataset is disabled.
• The diagram consistency state of the exported network diagrams is set as inconsistent.
• You can export an XML workspace document in the .zip file format to create a smaller, more portable file.

Caution:

The Export XML Workspace Document tool is not recommended for copying large amounts of geodatabase data with the default Data option. As an alternative, you can use an XML workspace document to transfer the dataset's schema between geodatabases; then, use the Append tool to import the data.

It is recommended that you enable the network topology and update any network diagrams after importing an XML workspace document into a new geodatabase.

Upgrade a trace network

You can upgrade a trace network dataset to take advantage of new functionality by applying schema changes in the information model. The ArcGIS Pro client version determines whether an upgrade is necessary.

The ArcGIS Pro version you're using determines the trace network version of the trace network dataset that is created. The ArcGIS Pro version also determines whether an upgrade is available for the trace network dataset. The table below lists the ArcGIS Pro release and corresponding Trace Network Version.

ArcGIS Pro releases and corresponding Trace Network Version created or upgraded with each release

ArcGIS Pro release	Trace Network Version
2.6.x	1
2.7.x	2
2.8.x	2
2.9.x	2
3.0.x	3

The version and upgrade history of the trace network can be viewed on the Trace Network tab of the Network Properties dialog box.

To upgrade a trace network dataset, use the Upgrade Dataset tool. Before the upgrade is attempted, the following must be completed:

• Save all edits.
• Obtain an exclusive lock; 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 the Dataset to upgrade parameter must be from a database connection with the versioning type set as branch.

To review specific schema changes for each version, see Trace network upgrade history.

Update the portal trace network owner

When working with an enterprise geodatabase, a trace network dataset has two owners that are used to control access for administrative tasks. In addition to the database user who creates a trace network, the active portal user account is recorded as the portal trace network owner. When a trace network is created, these owners are determined based on the user accounts for the database connection and active ArcGIS Enterprise portal.

• The database trace network owner is recorded as part of the fully qualified name of the utility network dataset.
• The portal trace network owner is stored as metadata for a utility network. You can view this metadata using the network properties when you access it 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 trace network. If the existing portal trace 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.

Learn more about how to manage content

ArcGIS platform compatibility

It is important to be aware of the compatibility between ArcGIS clients, the geodatabase, and the trace network dataset when working with various versions. Trace networks in an enterprise geodatabase 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 alone when working with a single-user deployment of the trace network.

Learn more about client and geodatabase compatibility

Trace network version

When a trace network is created, the version of ArcGIS Pro used is recorded on the Network Properties dialog box. This is located in the General section of the Trace Network tab for the ArcGIS Pro Release property. The Trace Network Version value is determined by the version of ArcGIS Pro used to create or upgrade the trace network dataset.

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 various versions, ArcGIS client applications (such as ArcGIS Pro and ArcGIS Enterprise) are backward compatible when working with the trace network:

• Later versions of ArcGIS Enterprise can share earlier versions of the trace network.
• Later versions of ArcGIS Pro can be used to view and edit earlier versions of the trace network.

This also means that earlier client software versions cannot open trace network datasets that participate in newer functionality. For example, ArcGIS Enterprise 10.9 cannot be used to share a Trace Network Version 3.

Note:

Trace Network Version 1 is only supported in a file geodatabase.

The table below outlines the ArcGIS platform compatibility for a trace network.

ArcGIS platform compatibility for a trace network

Trace network version	Compatible ArcGIS Pro version	Compatible ArcGIS Enterprise version
1	2.6 and later	Note: Trace Network Version 1 is not supported in an enterprise deployment.
2	2.7 and later	10.9 and later
3	3.0 and later	11 and later