The B_TraceConfigurations table allows you to define trace configurations.
| Field | Description |
|---|
Trace Configuration Name | The name of the trace configuration. |
Creator | The user that will own the trace configuration in the target utility network. |
Trace Type | Specifies the type of trace that will be configured. | Name | Description |
|---|
Connected | A connected trace that begins at one or more starting points and spans outward along connected features will be used. This is the default. | Subnetwork | A subnetwork trace that begins at one or more starting points and spans outward to encompass the extent of the subnetwork will be used. | Subnetwork_Controllers | A subnetwork controllers trace that locates sources and sinks on subnetwork controllers associated with a subnetwork will be used. | Upstream | An upstream trace that discovers features upstream from a location in the network will be used. | Downstream | A downstream trace that discovers features downstream from a location in the network will be used. | Loops | Loops are areas of the network where flow direction is ambiguous. A loops trace that spans outward from the starting point based on connectivity will be used. | Shortest_Path | A shortest path trace that identifies the shortest path between two starting points will be used. | Isolation | An isolation trace that discovers features that isolate an area of a network will be used. |
|
Description |
The description of the trace configuration. |
Tags | A set of tags used to identify the trace configuration. The tags
can be used in search and indexing. |
Trace Configuration | A Json object representing the collection of trace configuration parameters. |
Result Types | A Json object representing the types of results to return. |