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.
A 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.
Prepare for publishing
When you publish and consume a feature service that contains a trace network, the following conditions and prerequisites apply.
To prepare the environment for the publishing process, complete the following steps:
- Trace network 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.
License:
Organization members must be assigned a license for the ArcGIS Advanced Editing user type extension to create, publish, and edit a trace network in an enterprise geodatabase. Query and trace operations do not require this user type extension.
- Set the versioning type of the geodatabase connection to Branch before you add the trace network to the map.
- Right-click the database connection in the Catalog pane and click Geodatabase Connection Properties.
- On the Geodatabase Connection Properties dialog box, choose Branch under Versioning Type, and click OK.
Note:
Branch versions can only be edited using feature services. If the versioning type of the geodatabase connection is not set to branch versioning, you cannot publish a trace network.
- Register the feature dataset as versioned.
- Right-click the feature dataset and click Manage to open the Feature Dataset Properties dialog box.
- Check the Versioning check box and ensure that Branch is chosen.
- Click OK to register the feature dataset as branch versioned.
The trace network feature dataset is registered as branch versioned.
- Right-click the trace network in the Catalog pane, and click Add To New Map to add the trace network and its associated layers to a new map.
- When asked if you want to add all classes that participate in the trace network to the map, click Yes.
Note:
- While the service can still be consumed from the web, to consume the trace network in ArcGIS Pro, the map must contain all of the layers that participate in the network; otherwise, analyzer warning 24099 will be returned.
- Definition queries and hidden fields set using the Visible layer field property are not supported; analyzer error 00270 will be returned if these conditions exist.
- Ensure layer IDs have been preserved in the map document.
It is recommended that you manually assign layer IDs prior to publishing if you intend to overwrite the web layer or service in the future. Otherwise, service sublayer IDs can potentially change when the web layer or service is overwritten. This can cause problems with web clients accessing these services referencing specific layer IDs. You can enable this with the Allow assignment of unique numeric IDs for sharing web layers setting on the Map Properties dialog box.
- Right-click the map document heading in the Contents pane and click Properties.
- On the Map Properties dialog box, choose Allow assignment of unique numeric IDs for sharing web layers under the General tab and click OK.
If you choose not to manually assign layer IDs, 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.
Publish the trace network as a feature service
To publish a trace network as a editable feature service that supports analytic functionality such as tracing and diagram creation, complete the following steps:
- Ensure that the trace network and all its associated layers are added to the current map view.
Note:
The publishing map used to create a trace network feature service must not contain subtype group layers. - Click the Web Layer drop-down menu
on the Share tab and click
Publish Web Layer. - In the Share As Web Layer pane, on the General tab , enter a name for the web layer, and optionally, provide values for the Summary and Tags parameters.
- Under Data and Layer Type, choose Map Image, and check the Feature check box under Reference registered data.
Version Management is enabled on the Configuration tab, under Configure Layers
. - Under Location, under Portal Folder and Server and Folder, choose where the data will be shared.
You can share the data to the root folder or create a folder.
- For Sharing Level, specify how the trace network will be shared.
- On the Configuration tab, under Configure Layers , confirm that Version Management is enabled under Capabilities.
Note:
The Version Management option is not available if the Feature option is not enabled, or the feature dataset containing the trace network is not branch versioned.
- On the Configuration tab, under Layers, click the Configure Web Layer Properties button
next to Feature to open Feature Properties, and ensure that the Allow update of true curves and Only allow true curve updates by true curve clients options are checked under Properties. - Click Analyze to identify potential issues or errors.
Two types of analyzer messages appear on the Messages tab. Errors are issues that must be fixed before you can publish web layers. Warnings are issues in which performance, appearance, or data access may be affected. Double-click the error or warning for a solution or access to a help topic. Right-click the error or warning for suggestions on how to address the issue.
Tip:
You can register an enterprise geodatabase as a data store when publishing or analyzing the data. An analyzer error message appears in the Share As Web Layer pane if the database is not registered with the server. To register a geodatabase, click Options and click Register Data Source with Server on the error message. - Click Publish to publish the trace network.
- Add the trace network web layer to the map.
Publish trace network feature classes without a trace network layer
When sharing web feature layers for network feature classes without the trace network layer, the restrictions are lessened; however, this also prevents the ability to work with tracing and network diagrams.
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 layer 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. While the trace network dataset cannot be taken offline for editing, feature classes associated with the trace network 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