Disable Topology

Description

The disableTopology operation disables the network topology for a utility network. When the topology is disabled, feature and association edits do not generate dirty areas. Analytics and diagram generation can't be performed if the topology is not present.

When the topology is disabled, the following happens:

• All current rows in the topology tables are deleted.
• No dirty areas are generated from edits.
• Remaining errors and their associated dirty areas still exist and can be cleaned up.

Disabling the topology is supported both synchronously and asynchronously. To perform certain network configuration tasks, the network topology must be disabled.

• This operation must be run by the portal utility network owner.

• The topology can be disabled in the default version or in a named version. If disabled in a named version, it may not be later enabled in the named version. The reconcile process should be used to inherit the topology state from the default branch version.

Request parameters

1
f=html | json | pjson

1
async=true | false

JSON Response syntax

JSON response (when async = false):

1
2
3
4
5
6
7
8
9
{
  "moment" : <datetime>,
  "success" : <true | false>,
  "error" : {                   // only if success is false
    "extendedCode" : <HRESULT>,
    "message" : <error message>,
    "details" : [ <detail> ]
  }
}

JSON response (when async = true):

1
2
3
{
  "statusUrl" : <url>
}

JSON response to the status URL (when pending or in progress):

1
2
3
4
5
{
  "status" : "<Pending | InProgress>",
  "submissionTime" : <datetime>,
  "lastUpdatedTime" : <datetime>
 }

Example usage

Disable the network topology for a utility network using the disableTopology operation.

Request URL and parameters:

https://myserver.esri.com/server/rest/services/LandUse/UtilityNetworkServer/disableTopology

1
2
3
4
f=json
gdbVersion=SDE.DEFAULT
sessionID={29CC8FF6-D6C6-4157-A9A8-A9A9BCFE07D1}
async=false

JSON response:

1
2
3
4
{
 "moment": 1554393356246,
 "success": true
}