Latest Contributions by RobertKrisher

Esri uses partitioned tiers when the model allows each subnetwork to operate independently of the subnetworks above and below it. This means that each feature belongs to a single subnetwork with no persisted dependency or knowledge of any higher or lower-rank networks, it is only discoverable via outside of upstream/downstream tracing. Hierarchical networks are used when subnetworks are considered nested. That is to say that one subnetwork will act as a form of "ultimate source" that supplies/receives all the resources in an area (wastewater treatment plant, water wells, gas custody transfer meters). The lower-rank subnetworks then subdivide this higher-level system into smaller and smaller zones based on different criteria (pressure reducers, pumps, compressors, lift stations). The following diagram below shows how water tiers are nested in each other with water sources creating a Water System, pumps/pressure valves providing Water Pressure zones, and system valves allowing a utility to further refine their territory into Water Isolation zones. In a hierarchical network each feature belongs to multiple subnetworks, and as such has multiple subnetwork fields (SystemSubnetworkName, PressuresubnetworkName, IsolationSubnetworkName). ... View more

If you're using ArcGIS Pro you can also use the data engineering tools to analyze the contents of your table. On of the statistics they could for fields is how many null values there are: https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/data-engineering/view-statistics.htm. ... View more

The AWS RDS engine are you using will determine the syntax you should use. If you're using one of the engines listed above then it should work (although we didn't test against AWS RDS) as long as you use the exact SQL provided. If you're using Amazon Aurora or one of the engines we didn't provide a syntax for then that would explain the syntax error. ... View more

Make sure you've copied the entire procedure statement into your query editor. I just tested the expression in this article against a local PostgreSQL 13 database. If you read the accompanying blog post you'll see that I recommend that you keep your materialized views simple and only maintain a single materialized view for each of your branch versioned tables. Any filtering, combining, or translating of data should be done with a reporting layer on top of the materialized views. This can be done by creating regular views against the materialized views, or by using some sort of reporting/business intelligence tool. ... View more

Based on the drawing provided it would seem like you would want to have approved and in-service be included in the networks (in your description you said you wanted to have approved be not traceable). Is there a reason why you wouldn't just modify the existing condition barrier to reference these different states? The only reason I could think of is that you are also considering using it to manage other situations / multiple fields, which is what Mike has alluded to in his comments. ... View more

There are no web hooks for any of these operations, but the version infos method of the version management service will allow you to see the last reconcile date of a version. ... View more

Check the parameters in your tool. I've found that if i open the dialog with something that doesn't auto-populate those parameters (like a subnetwork trace) then switch over to something that does require those parameters (like an upstream trace) that the tool doesn't automatically pick up the starting locations / barriers from my map. You can run into the same issue if you're building a python script or a model to automate tracing tasks. ... View more

Glad to hear it worked! Strategies for keeping dirty areas in check is a good topic for a different thread 🙂 ... View more

If you haven't already, I'd recommend logging a case with support on this. ... View more

To my knowledge there isn't a way to configure which terminal appears first. ... View more

If you are still experiencing the issue I would recommend logging a case with support. This issue will likely walking through on a call with your code + data. Based off that error message my guess is there is an invalid character in your subnetwork controller name or subnetwork name. If you try to enable the controller manually you should be able to see a more specific error. ... View more

@Anonymous User If you want to include these features in your network as energized features you could add a new set of asset groups / types to your device layer. This can be a bit of a heavy lift, so if you're just doing this for asset management / work management purposes and don't need to trace / export these features you could consider adding several standalone feature classes / tables to track these assets, registering them as branch versioned, and including them in your utility network service. ... View more