Latest Contributions by RobertKrisher

In cases where you need a different field alias depending on the subtype, subtype group layers are currently the only means of achieving this. However, the process can be made significantly less tedious and manual by using something like the utility network properties extractor to export your field configurations to a spreadsheet (once) and then applying those properties to any derived map products you have. Once you get used to setting field properties in this manner it isn't too different from how we've historically had to think about maintaining the dozens of different web maps used by a utility, where every field map has a different set of field order, visibility, and alias. ... View more

The export associations geoprocessing tool will export all the associations in the utility network (UN_X_Associations) to a csv file. If you're looking for a csv file of all the association ROLES then you'll need to use a tool like the utility network properties extractor (pre 3.2) or the generate schema report tool (3.2 or later) to export your utility network schema to a csv file. If you're saying that you have associations in your database and the export associations tool is producing a blank csv file, open a case with support. ... View more

The utility network is not supported in ArcGIS Online, so if you attempt to copy data to ArcGIS Online that contains a utility network (and all its system tables) it will fail. When you create the service that you want to share, don't include the utility network and it will copy the classes from your utility network but will not include any of the system tables that AGOL cannot understand. ... View more

@NadiaAlami all the system valves in the model have the isolating category assigned to them. You'd use the advice I gave above which is to set a filter barrier for the category of isolating. If you were worried about whether the valves were accessible or operable (and you maintained such attribution) you could also include those in your filter barrier. ... View more

@NadiaAlami The answer to this is similar to the answer to your other post about downstream tracing. Your water distribution system, like most, is heavily looped. An upstream trace shows you all the potential paths that water can take to get to a location, so the result returned is correct, even if some paths are only contributing a small fraction of a percent of water. It sounds like you want to see the shortest path to your subnetwork controller, which you can accomplish by running a subnetwork controller trace then running a shortest path trace between your subnetwork controllers. The shortest path trace will find the shortest path between ONLY TWO points, so if you have multiple controllers you will need to either pick just one of them or iterate through all of them and merge the results. ... View more

@rlyding If you are using the current sewer utility network foundation this is the expected behavior, however in the upcoming model, this terminal has been enhanced to include more path options that allow for more control between the upstream and downstream paths. That is because the paths of the default terminal configuration of a directional manhole is "all". This means that there is a two-way path from upstream to upstream 2 as well as a two-way path from downstream to downstream 2. The following diagram represents the 'internal connectivity' of the paths for the directional manhole terminal configuration:   If you wish to separate the upstream and downstream terminals into mutually exclusive paths, you will need to create a terminal configuration with a specific set of paths that don' allow for that. If you're still in the implementation phase of your utility network, you can adjust the existing terminal configuration in your asset package. If you're already in production, the process will be more involved. For reference, this is what the terminal configurations in the newer data model are expected to look like:     ... View more