Publish and consume services with a trace network

Available with Standard or Advanced license.

Beginning with ArcGIS Enterprise 10.9, when you publish or consume a service that contains a trace network and related network feature classes, some conditions and restrictions apply. These are dependent on the layers that are present in the map view, how the map service is configured, and where the service will be consumed.

Publish a trace network layer

There are conditions and restrictions for sharing trace network and related feature classes as web layers. Analyzer errors are returned when these rules are broken, to prevent publishing. Additional analyzer warnings alert you if your intention is to consume services using ArcGIS Pro.

  • The published feature service automatically includes the Trace Network and Network Diagram services to support trace analysis and network diagrams. See Trace network services to learn more.
  • The federated server for the portal must be ArcGIS Server 10.9 or later.

When the trace network layer is present in the active map view, the applicable conditions and restrictions for sharing are as follows:

  • Map layers must be from a database connection established as the database trace network owner.
  • The connected ArcGIS Enterprise portal account must be the portal trace network owner.
    The active portal account must be licensed with the ArcGIS Trace Network user type extension to create, publish, and work with a trace network in an enterprise geodatabase.
  • Definition queries and hidden fields set using the Visible field property are not supported—analyzer errors will be returned if these exist.
  • The map must contain all of the layers that participate in the trace network if the intent is to consume in ArcGIS Pro.
    • An analyzer warning will be returned if a subset of trace network layers is provided. This is displayed to warn about issues that will arise when consuming services in ArcGIS Pro that were published with a subset of trace network layers.
  • Web layers must reference data from registered data sources; in the Share As Web Layer pane, on the General tab and under Data and Layer Type, ensure that Map Image is selected under Reference registered data.
  • Include Feature to have access to the trace network layer, the ability to make edits on the default branch version, or the ability to enable the version management capability.
  • Optionally, uncheck the Ensure map is set to allow assignment of unique IDs check box. If the box is checked, an analyzer error will be returned if the Allow assignment of unique numeric IDs for sharing web layers option in Map Properties is not enabled. If the box is unchecked, the analyzer is skipped. See Configure a web feature layer to learn more.
  • All network layers must be registered as branch versioned.
    • Version Management is an optional supported capability. Review Share branch versioned data to understand the conditions enforced by analyzers for branch versioned datasets.

Publish trace network feature classes without a trace network layer

When sharing network feature classes without the trace network layer, the restrictions are lessened. In this case, you can configure the active map view to include a subset of layers using definition queries, make a subset of fields visible, and so on. This allows an organization to share the services and maps with users who require access to a subset of trace network classes.

When the trace network layer is not present in the active map view, the application conditions and restrictions for sharing are as follows:

  • The published feature service will not include the Trace Network or Network Diagram secondary services—performing trace analysis or working with network diagrams will not be supported.
  • The map layers being published can support definition queries and hidden fields set using the Visible field property.
  • This feature service will behave in the same way as any other feature service. Any edits will still apply trace network behavior behind the service (such as dirty area creation), but dirty areas and error features will not be visible on the map.
  • The version management capability is optionally supported.

Workflow examples

To understand these conditions for working with services and the trace network, consider the following examples:

GIS editor workflows

A GIS editor is making edits to correct issues identified with a hydro network. That editor needs to see dirty areas and the error features created by edits. The editor will use a feature service created with all of the data and the trace network layer. The ArcGIS Pro project created for this user would contain the trace network layer and all associated network layers.

GIS analyst workflows

A GIS analyst working with a hydro network needs to perform tracing as well as perform other analysis, and map production. The analyst uses a feature service created with all the data and the trace network layer. The ArcGIS Pro project created for this user would contain the trace network layer and all associated network layers.

In this workflow, the GIS analyst needs permission to the whole feature service.

Web access and field editor workflows

Casual users may use web maps configured for specific tasks and workflows. These web maps are usually configured from feature services with a reduced set of layers, and may include definition queries or a reduced set of visible fields on some layers. When a user only needs to view or query data, the web map can use a feature service without a trace network layer.

Field editors typically use either Esri mobile apps or runtime apps created by Esri partners to perform limited edits for field operations. If a workflow requires tracing or network diagrams, the web map will need to use a feature service that includes the trace network service and network diagram service. As with general web access workflows, simple field editing workflows may consume a web map that contains a feature service without the trace network layer, as it will not be necessary in this workflow to display dirty areas or error features.

Some workflows may also require access to data when internet connectivity is inconsistent or unavailable. When the trace network layer itself is not needed, trace network data can be taken offline for viewing or editing using a web map. Taking web maps offline allows you to view, collect, and update features when you are disconnected from the internet. To work with your trace network data offline, you must first enable the sync capability on all web layers used in your map's feature services by checking the Enable Sync check box on the Configuration tab of the Share As Web Layer pane. The sync capability has operations that allow clients to work with a local copy of the data. When editing is enabled on the feature service, clients can edit the local copy of the data and synchronize when connectivity is available.

Learn more about working with offline maps and branch versioned data