Available with Standard or Advanced license.
Configuration and management tasks within the utility network are dependent on many factors, including the type of workspace connection and its permission level, state of the network topology, and the version being referenced.
The following sections provide an overview of the dependencies that exist when working with a utility network. For more details on usage and examples, reference An overview of the Utility Network toolbox.
Caution:
Certain network configuration tasks cannot be changed or are only allowed prior to enabling the network topology for the first time. Review Network topology state in the tables below for details on tools and actions impacted.Network configuration tasks
The following tables summarize different types of network actions with the following details:
- Action—The tool or type of action being performed
- Network topology state—The required state of the network topology
- Enabled
- Disabled
- Prior to initial enabling of network topology
- Currently not allowed
The following only apply when working with a utility network with an enterprise geodatabase:
- Workspace—Specifies the required data source.
- Service—The action must be performed against a feature layer from a service.
- Database connection—The action must be performed against a database connection. For operations completed using a database connection, always ensure the workspace is set to branch for the versioning type.
- Versioned data required—Specifies whether the action requires the dataset to be registered as versioned. The versioning type must be branch.
- Database and portal utility network owner connection required—Specifies whether the action requires connections as both the database owner and portal owner of the utility network.
General Operations
Action | Workspace | Network topology state | Default version only | Versioned data required | Database and portal utility network owner connection required |
---|---|---|---|---|---|
Create Utility Network | Database connection | Disabled | Yes | No | Yes |
Enable Network Topology | Database connection or service | Disabled | Yes | Yes | Yes |
Enable Network Topology (generate errors) | Database connection | Disabled | Yes | No | Yes |
Disable Network Topology | Database connection or service | Enabled | No | No | Yes |
Validate Network Topology | Service | Enabled | No | Yes | No |
Update Portal Dataset Owner | Database connection | Enabled/Disabled | No | Yes | Requires connection as the database utility network owner |
Network modifications
Action | Workspace | Network topology state | Default version only | Versioned data required | Database and portal utility network owner connection required |
---|---|---|---|---|---|
Load data | Database connection or service | Enabled/Disabled | No | No | No |
Update service territory feature class extent | Currently not allowed | N/A | N/A | N/A | N/A |
Tip:
A disabled network topology state is recommended for larger data loading operations.
Editing a network
Action | Workspace | Network topology state | Default version only | Versioned data required | Database and portal utility network owner connection required |
---|---|---|---|---|---|
Create feature templates | Database connection | Enabled/Disabled | No | No | No |
Edit features and attributes | Service | Enabled | No | Yes | No |
Modify associations | Service | Enabled/Disabled | No | Yes | No |
Service | Enabled/Disabled | No | Yes | No | |
Service | Enabled/Disabled | No | Yes | No | |
Database connection or service | Enabled/Disabled | No | Can be from a database connection (if unversioned). If versioned, it must be from a service. | Yes | |
Update Subnetwork | Service | Enabled | No | Yes | No |
Update Is Connected | Service | Enabled | No | Yes | No |
Importing and exporting information
Action | Workspace | Network topology state | Default version only | Versioned data required | Database and portal utility network owner connection required |
---|---|---|---|---|---|
Export Associations | Database connection | Enabled/Disabled | No | No | Requires connection as the database utility network owner |
Import Associations | Database connection | Enabled/Disabled | No | No | Requires connection as the database utility network owner |
Import Rules | Database connection | Disabled | Yes | No | Yes |
Export Rules | Database connection | Enabled/Disabled | No | No | Yes |
Export Subnetwork (without acknowledgements) | Service | Enabled | Yes | Yes | No |
Export Subnetwork (with acknowledgements) | Service | Enabled | Yes | Yes | Requires connection as the portal utility network owner |
Database connection | Enabled/Disabled | No | No | Requires connection as the database utility network owner | |
Export Subnetwork Controllers | Database connection | Enabled/Disabled | No | No | Requires connection as the database utility network owner |
Tip:
A disabled network topology state is recommended to import a large number of associations or subnetwork controllers.
Modifying components
Action | Workspace | Network topology state | Default version only | Versioned data required | Database and portal utility network owner connection required |
---|---|---|---|---|---|
Add Domain Network | Database connection | Disabled | Yes | No | Yes |
Delete a domain network | N/A | Currently not allowed | N/A | N/A | N/A |
Add Network Attribute | Database connection | Disabled | Yes | No | Yes |
Set Network Attribute | Database connection | Disabled | Yes | No | Yes |
Delete a network attribute | N/A | Currently not allowed | N/A | N/A | N/A |
Add Terminal Configuration | Database connection | Disabled | Yes | No | Yes |
Set Terminal Configuration | Database connection | Disabled | Yes | No | Yes |
Delete Terminal Configuration | Database connection | Disabled, must be performed prior to the network topology being enabled for the first time | Yes | No | Yes |
Remove a terminal configuration assignment—modify terminal configuration set from a user-defined terminal configuration to the default of Single Terminal | Database connection | Disabled, must be performed prior to the network topology being enabled for the first time | Yes | No | Yes |
Set Network Category | Database connection | Disabled | Yes | No | Yes |
Add Network Category | Database connection | Disabled | Yes | No | Yes |
Delete Network Category | Database connection | Disabled | Yes | No | Yes |
Add Tier | Database connection | Disabled | Yes | No | Yes |
Delete a tier | N/A | Currently not allowed | N/A | N/A | N/A |
Add Tier Group | Database connection | Disabled | Yes | No | Yes |
Database connection | Disabled | Yes | No | Yes | |
Add Rule | Database connection | Disabled | Yes | No | Yes |
Delete Rule | Database connection | Disabled | Yes | No | Yes |
Set Association Role | Database connection | Disabled | Yes | No | Yes |
Set Association Role (unassign) | Database connection | Disabled, must be performed prior to the network topology being enabled for the first time | Yes | No | Yes |
Set Edge Connectivity (modify from EndVertex to AnyVertex) | Database connection | Disabled | Yes | No | Yes |
Add subtypes to Asset group field | Database connection | Disabled | Yes | No | Yes |
Edit or delete subtypes assigned to Asset group field | N/A | Currently not allowed | N/A | N/A | N/A |
Add domain values to Asset group field | Database connection | Disabled | Yes | No | Yes |
Edit or delete domains assigned to Asset type field | N/A | Currently not allowed | N/A | N/A | N/A |