Latest Contributions by RobertKrisher

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

Please open a case with support on this. Seeing a blank error message like that means something unexpected is happening. ... View more

Yes, but only the subnetworks that have been edited and validated. And even then, this is only if the subnetworks are configured to use the status field. Most water and gas customers choose to not use the status field, while electric customers do. ... View more

@MarianoDiNapoli btw, if all you need to do is update some asset type/asset group descriptions, you can do that on your utility network using ArcGIS Pro 3.7. You don't even need to disable the network topology. You can do this using the Design Views or the new Alter Subtype and Alter Coded Value Description tools ... View more

It sounds like you are staging and deploying your utility network in the same geodatabase as your asset package. this is not supported. ... 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

The UN_* tables are the system tables of the utility network, the C_* tables are the corresponding tables in the asset package. You shouldn't be redeploying the asset package to the same geodatabase to make configuration changes, you have to deploy it to a new geodatabase. There asset package is designed to append new data and new configuration into a utility network. If you make changes to an asset package you must deploy it to a new geodatabase, otherwise you will end up with duplicated data and it's likely that most of the configuration changes will not be applied. ... View more

@GISP00 glad to hear that worked. that's something I was going to suggest, when you're relying on a foreign key that isn't always populated on a table to migrate a relationship, its a good idea to put a filter to only try and create associations when the field is populated so you don't get any unnecessary warnings. This is especially important when a class can have multiple relationships (transformer > pole, transformer > vault, transformer > pad). ... View more

@GISP00  the tutorial was last tested on 3.6, but it is works for 3.5 as well. ... View more

I'll let @MikeMillerGIS handle questions about create migration workspace, but you should also look at a newer way to migrate relationships described in this tutorial: Migrate relationship classes to a utility network | Documentation This new approach allows you to map the relationship directly to the associations table, which means that you'll get the latest relationships every time you run the data loading tools. The older approach creates a static CSV file when you create your migration workspace, which leads to relationships and features getting out of sync over time. ... 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

Correct, a terminal configuration cannot be modified once created. You can set a terminal configuration of an asset type, but it cannot be modified. While these restrictions might be loosened in the future (with additional checks, safeguards, and specific restrictions) this currently requires going back to an asset package. ... View more

Glad you got it working! The trace should always have been working, but if you were relying on update subnetwork then my guess is you were working in a version and not on default. ... View more

Once you've created the network attribute you must assign it to each field/class you want to associate with that network attribute then you must ensure that the field on each class is populated with the desired values. ... View more

When you run the trace, where does it stop? What is the phasing of the transformer? Can you post a screenshot of the subnetwork definition for this tier from the network properties dialog? You have a non-standard model, so I want to see how your propagators are configured? You'll need to scroll all the way to the right to see these properties:   ... View more