Latest Contributions by RobertKrisher

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

The warning you're getting about duplicated rows is caused because the asset package tools are detecting duplicate rows in the asset package. Because you are deploying the asset package to a new geodatabse, you cannot have conflicts between what is in the asset package and the target UN (because the target UN is empty). When you run export to asset package the resulting asset package will not contain any UN_* tables, so we populate C_* tables so they can be used to recreate the data in the system tables when the asset package is deployed. ... View more

That is just one way of modeling a transformer. since you have chosen to model them using containment/associations you will use the modify associations tool to create those associations. When creating features by hand you should be using an editing template that includes all these features, along with their associations, so users don't need to perform these manual steps every time a feature is created. You can learn more about that tool in the ArcGIS Online Help; Associations | ArcGIS Pro documentation You can also find a tutorial with examples of how to populate associations here: Get started with ArcGIS Utility Network for electric | Documentation ... View more