- URL:
- https://<root>/<serviceName>/NetworkDiagramServer/findDiagramNames
- Methods:
POST- Version Introduced:
- 10.6
Description
The find operation retrieves the set of diagrams that cover a given extent, verify a particular WHERE clause, or contain specific network elements or diagram features. It is performed on a Network Diagram Service resource. The result of this operation is an array of strings, each one corresponding to a network diagram name.
Request parameters
| Parameter | Details |
|---|---|
|
The name of the geodatabase version. Syntax: Example: |
|
The token (guid) used to lock the version. Syntax: Example: |
|
The session moment. Syntax: Example: |
| A JSON envelope object representing the extent that you want the network extent of the resulting diagrams to intersect. Syntax: Example: Retrieve published network diagrams in which networkExtent intersects a given envelope: |
| A WHERE clause for the query filter. Any legal SQL WHERE clause operating on some fields in the DIAGRAMS table is allowed. See the network diagram fields section below for the exact list of field names that can be used in this WHERE clause. Syntax: Example: |
| A set of network element Global IDs, or network diagram feature Global IDs represented in a given diagram that are included in the resulting queried diagrams. This parameter is a JSON object composed of two items:
Syntax: Example: Case 1—Retrieve published network diagrams including the utility network junction with globalID = {48509846-410E-4042-A158-EFD1813567A7}: Case 2—Retrieve published network diagrams including utility network features associated with the diagram feature contained in diagram "Basic_RMT003" with diagram feature globalID = {2072E89B-BAE8-4495-A765-FC7EDF7E373F}: |
| A boolean statement that specifies whether to exclude subnetwork system diagrams.
Syntax: Example: |
|
The response format. The default response format is html. Values: |
Network diagram fields for the WHERE clause
| Field name to use in the WHERE clause | Data type | Related item in the JSON diagram info object |
|---|---|---|
NAME | String | name |
USERTAG | String | tag |
CREATIONDATE | Date | creationDate |
CREATOR | String | creator |
LASTUPDATE | Date | lastUpdateDate |
UPDATEDBY | String | lastUpdateBy |
Example usage
Retrieve all diagrams in version ABV1 referencing utility network features for which Global IDs are {F8199534-8B77-4D26-8C3C-8A55DB66728E}, {5AD29D27-0BBE-4DD9-AFD4-3AFE22CE93F9}, or {95FB5F92-90A1-4EF7-AAC0-353599D3789B}:
-
URL:
https://myserver.esri.com/server/rest/services/Naperville/Network Diagram Server/find Diagram Names -
Parameters:
Use dark colors for code blocks Copy gdbVersion=ABV1 sessionId= moment= extent= where= features={"globalIDs":["{F8199534-8B77-4D26-8C3C-8A55DB66728E}","{5AD29D27-0BBE-4DD9-AFD4-3AFE22CE93F9}","{95FB5F92-90A1-4EF7-AAC0-353599D3789B}"]} f=pjson -
Sent URL (GET):
https://myserver.esri.com/server/rest/services/Naperville/Network Diagram Server/find Diagram Names?gdb Version=ABV1&session Id=&moment=&extent=&where=&features=%7B%22global IDs%22%3A%5B%22%7BF8199534-8B77-4D26-8C3C-8A55DB66728E%7D%22%2C%22%7B5AD29D27-0BBE-4DD9-AFD4-3AFE22CE93F9%7D%22%2C%22%7B95FB5F92-90A1-4EF7-AAC0-353599D3789B%7D%22%5D%7D&f=pjson
JSON Response syntax
An array of strings, each one corresponding to a diagram name.
{
"diagramNames": [
"< diagramName1 >",
"...",
"< diagramNameN >"
]
}JSON Response example
{
"diagramNames": [
"Basic_Network891G25RT2",
"DiagramTest3"
]
}