Latest Contributions by RobertKrisher

Thanks for the info! It looks like this could be BUG-000184727, which is currently scheduled to be included in the next 11.3 patch. Support should be able to confirm the details of the bug, patch, etc. especially if you have a reproducible test case. ... View more

@EdwardBlair if you really need to hide that feature you can add an output condition to the trace that will explicitly hide it. In this case, adding an output condition where the category is not equal to E:Fuse. I apologize for using screenshots of water data for this issue, I was having issues finding a spot in the electric project I was using where the fuses had terminals. ... View more

You can find the comprehensive list of which changes require disabling the network topology or are not allowed on utility network management tasks page. Schema changes that do not affect the utility network do not require disabling the network topology. Adding or removing a new field to a class the belongs to a utility network does not require disabling the network topology, as long as those fields don't have any network attributes associated with them. ... View more

Even if you could intercept that call, I'm not sure how you would achieve what you're looking for? A simpler approach in this case might be to create an attribute rule that runs on create and update on the subnetwork line that reads the user partition information from the first active subnetwork controller for the subnetwork. ... View more

You'll need to weigh the business value of having more granular network with the time it takes to manage all the individual networks. Individual subnetworks will trace and update quickly, but the biggest problem with managing a dataset with many thousands of subnetworks is the amount of time it takes to update ALL your subnetworks. This means you need to account for this additional time when you first go live, and every time you need to disable/enable your network topology to make schema changes. An alternative would be to only model subnetworks at the transformer level, and for the fuse-level transformers use something like the batch trace tool to calculate the individual fuse-level circuits. Note: ArcGIS Pro 3.7 introduces an optimization that allows the first time you run update subnetwork to be significantly faster, that will help with your initial deployment. I recommend you test this. ... View more

Stop points are only used by the Path trace. We describe the Path trace and the new parameters you're seeing in this article: What's new for ArcGIS Utility Network with the 2026 Network Management Release ... View more

If you want to have additional descriptive information about a subnetwork, I recommend you create a lookup table that contains these values then put an arcade expression on the popup for the subnetwork line and subnetworks table that displays this informaiton.  It is possible to add user-defined fields to this table and populate it using an attribute rule, but this adds additional overhead to each call of update subnetwork. For spatial queries you get into weird situations where you can be in multiple regions, for non-spatial queries you need to either create a lookup table or do even MORE processing. Putting all this information in a separate lookup table that is maintained as needed by administrators is a much more scalable solution, since it is only updated when it needs to be instead of every time update subnetwork is run. If you add a new user field to the subnetwork line class you can populate it using an attribute rule. It appears as read-only in ArcGIS Pro because we don't allow you to directly edit this class from a client (web, desktop, etc), but Attribute Rules are allowed to populate non-system managed fields.   ... View more