Latest Contributions by RobertKrisher

‎08-18-2025

1 - Operable is a network attribute for the device class, so any features that have a value populated will have their value used during analysis. Technically a cleanout isn't operable, but if you set it as Operable=No, and do a trace finding the first upstream inoperable device in your network, then it can be returned. Most attributes like this are either nullable or have an unknown or not applicable value. 2 - Based on the screenshot it looks like you are referring to the subtype group layers. If you click Add Data > Subtype Group Layer and select a class that has subtypes then it will add a special group layer that looks like that to your map. This is not exclusive to the utility network, but it is heavily relied upon by many utility network customers. If you follow the tutorial for configuring a map that I linked, you will learn about subtype group layeres.

‎08-15-2025

@egcon27 Please open a case with support. This is a known issue (workaround provided above). The fix for this should be out in the next patch for ArcGIS Pro 3.5.

‎08-15-2025

@Jens_Dalsgaard Ah yes, solving for the ad-hoc scenario. Ideally, you set up network categories (and even trace configurations) to cover 80-90% of your use cases (doing this at the asset group level is a good start). Then, a user needs to fine-tune the results in an ad-hoc trace that isn't already covered the user can add additional conditions to cherry pick specific asset types. Network Source, Asset Group, and Asset Type are all network attributes that you can include in conditional expressions on v6 or later networks. Setting up network categories for asset groups lets you skip having to make the user memorize network source ids and subtype codes which are not easily discoverable to an end user.

‎08-14-2025

Every link I reference below is contained on the Wastewater utility network reading list. The article you reference was originally published in 2018 (last updated in 2023). Most of what is outlined is still available in the Utility Network Foundations, but the way it is delivered is changed. I'll reach out to someone from Solutions for more comment, and see if they can update the article to avoid future confusion. 1 - The operable field does have a domain configured, but only for certain subtypes. As an example, system valves are operable but relief valves aren't. You can verify this by using the subtypes pane in ArcGIS Pro or by referring to the data dictionary. 2 - I'm not sure what you mean by clean lines? If you just add the utility network to a map it won't contain any symbology, but you can repoint the layers in the provided map to your migrated data if you want to use that symbology. If you want to configure your own map, with your own symbology, there's a tutorial for that: https://learn.arcgis.com/en/projects/configure-a-map-for-arcgis-utility-network/ 3 - Because your system is gravity fed, you should be able to use Digitized Direction tracing to do upstream/downstream tracing without loading subnetwork controllers (relevant article). I'd recommend you use the Modify Subnetwork Controller tool to manually create your subnetworks the first time before you attempt to automate this. Especially since the first time you create your subnetwork you may run into connectivity issues (relevant tutorial for creating subnetworks, subnetwork errors, and quality assurance). If you're implementing a foundation you could automatically create any sinks in your network as subnetwork controllers by migrating them into the C_Subnetworks table in your asset package. This will only work for asset types that are configured to be subnetwork controllers (treatment plant, directional manhole controllers, etc).

‎08-14-2025

Can you please confirm the following: After running append, the version differences tool shows the changes in your version. Please post a screenshot or python snippet including all the parameters you're using for reconcile (if you're using a GP tool) Show the version differences dialog after running reconcile. As long as you didn't post, all the changes that were in your version before the reconcile should be there after the reconcile. But, as @gis_KIWI4 noted, it won't show any of the perceived changes to data caused by the reconcile with default. This is because those differences are changes that were applied to your version, but are rather differences that were applied to default that your version now sees. If you are concerned that there is a bug, you should consider opening a case with support.

‎08-13-2025

@Jens_Dalsgaard Even outside of batch tracing, its a good idea to have network categories set up for the important types of features you care about. I use them all the time when setting up traces to focus on particular features of interest (medium voltage conductors, transformers, etc). I like them primarily for the following reasons: They let me identify a feature using a single network attribute, instead of needing to rely on the network source, asset group, and asset type. I prefer this not only for simplicity but also slight performance gains (which is important when you're doing a lot of these). They allow me to write code based on an abstraction (network category) instead of a physical implementation detail (asset group/type code). This makes my solution more portable. Because network categories can be applied to multiple asset types, this also gives me flexibility. I can assign/remove categories from different asset types to get the desired results in my report without needing to change any code. Being able to configure behaviors instead of hard coding checks for custom codes is especially important when you consider how much flexibility customers have with their data models and how much work it can take to update and deploy an add-in, script, or server component.

‎08-12-2025

As long as you're appending edits to the version using Esri software (GP Append, Cursors, Arcade, etc), you cannot bypass the logic used to track branch version changes. If you could, this would mean that the changes wouldn't show up in your version. What could be happening is that your code is applying the edits directly to default (which is easy to verify) or there is an error that is happening that is canceling and rolling back the edit operation, which should be presented through the UI or caught by your script..

‎08-11-2025

@Yeaton Modeling all your catchments as network features is possible, but there is already a mechanism in place in the stormwater model for tracking catchment features using subnetworks. Most customers have their catchment layer in the same feature dataset as the utility network, for visualization purposes, but don't include it in the network. If you do include these polygon layers in your map, then you'll need to be prepared to redraw the polygons every time an inlet is added, deleted, or moved. If you do go down this route, I wouldn't set up containment for all the features in the catchment. I'd recommend you only track the inlets (or other inflow locations) as content to the catchment, since they are the ties between the surface and underground systems. This also significantly reduces the number of associations you'll need to manage. If you still want to do this, you'll need to add a new asset group (a subtype) and asset types to the structure boundary class to represent them. You can find an outline of how to do this in the Configure a utility network topic in the ArcGIS Online Help.

‎08-06-2025

Arcade is not well suited to heavy data processing tasks like this, think of Attribute Rules like triggers. Even when they are set to be batch rules that just means execution is deferred. Each attribute rule is run on each feature. When you run a batch rule on 250 features, you are fetching all that data and recreating the association lines 250 times, once for each feature. I recommend that you rewrite the process to use Python; it should be significantly faster. This lets you fetch all the data and do all your analysis once, then push all the updates to your 250 features. (instead of rerunning the analysis 250 times). To help get you started I'd recommend you use the Create Association Lines tool to turn all the associations into lines.

‎08-06-2025

@JürgenBiendara subtype group layers are not selectable for the same reason that group layers aren't selectable, they are just group layers. If you want to toggle the selectability of a subtype group layer you'll need to iterate through all of its child layer and toggle their selectability (which can be accomplished using ArcPy).

‎08-05-2025

Instead of deleting the vertices, I would just enable the snapping grid and orient it between the two vertices I want to snap the laterals to. Then I would move all the features along that section of pipe to the snapping grid. The snapping grid will also help you deal with truing up any of the features that may have been connected to the lateral like service valves, corp stops, etc. In order for two lines to be connected, they must have a vertex at a common endpoint (endpoint to endpoint, or endpoint to midspan vertex). Even if you delete those vertices, as soon as you move the fitting at the end of the lateral back onto the main it will create a vertex on the main at that location.

‎08-05-2025

Please log a case with support so they can look at your versions, patches, etc. It shouldn't take that long to post so few edits.

‎08-05-2025

I recommend you check out the Arcade documentation for that method for the possible values for the association type parameter: FeatureSet functions | ArcGIS Arcade | Esri Developer. I don't see 'connectivity' listed as a valid value. Depending on the type of connectivity you're looking for, you should be able to use one of the other association types.

‎08-04-2025

Are you saying the post itself is taking over 10 minutes? or that the update subnetwork is taking over 10 minutes?

‎08-01-2025

Ed, Validate topology in conjunction with dirty areas does what you're looking for. What the 'Force Rebuild' option handles is when something goes wrong, and a dirty area doesn't get created or properly updated. This happens significantly less often that the issues we had with the GN which was constantly live stitching edits on the fly.

Online Status	Offline
Date Last Visited	Tuesday

My Ideas

Latest Contributions by RobertKrisher

Re: Sewer Utility Network Foundation

Re: ERROR 160021: Topology errors and dirty areas/objects may not be directly modified (sewer expanded)

Re: Batch trace - How to get count and write this to starting points

Re: Sewer Utility Network Foundation

Re: Reconcile of Branch Version not displaying Changes

Re: Batch trace - How to get count and write this to starting points

Re: Reconcile of Branch Version not displaying Changes

Re: Add custom feature layer to Utility Network Solution

Re: Issue with Fetching Connectivity Association using Arcade

Re: IsSelectable property of subtype layers

Re: Water service lines aren't re-snapping to main with vertex edits

Re: Increased version Post time when updating subnets

Re: Issue with Fetching Connectivity Association using Arcade

Re: Increased version Post time when updating subnets

Re: Corrupt network features in the U/N

Re: How to sync my Utility network geodatabase wit...

Re: Pre UN migration data cleanup workflows

Re: Best practices for managing and validating Uti...

Re: Pre UN migration data cleanup workflows

Re: Can one web map hold two separate utility netw...

European Utility Network Community (UNC)

APAC Utilities Community of Practice