Latest Contributions by RobertKrisher

@GavinMcGhieAs Mike said, there shouldn't be any problem with just adding the rule. It is my understanding that test points typically measure the current on the line that is connected to the anode, and not the anode itself (as seen in this article I'm sure you've read). This means that a test point's test wire is expected to be connected to a bonding line or cable, that wire is then connected to an anode. That is why the rules are configured that way. If your GIS doesn't have this level of detail or your test points are directly connected to your anodes via test wire in the field, add the rule. ... View more

Yes, you can add new asset types after deploying a utility network, but you must disable the network topology. This is convenient because you'll also need to disable the network topology to make other configuration changes like adding rules, adding the asset type to any subnetwork definitions, etc. I recommend you check out the configuration changes section of the utility network management tasks for the full list of what you can and can't do (and when).  Pay special attention to tasks that aren't allowed or "must be performed prior to the network topology being enabled for the first time". ... View more

Unfortunately, junction edge rules only determine which features are allowed to connect but don't control the cardinality of the features that are allowed to connect. To do something like that you'd need to write something like a validation attribute rule to enforce the cardinality of connected lines. ... View more

@NadiaAlami thank you for sharing this link, it was able to confirm my hypothesis (about the solution and that it was from a business partner). The web map that is being used has had normal group layers added to it with multiple copies of the device and layers added to it with definition queries applied. They describe this step in their previous video that shows you how to create the web map (https://youtu.be/rgUG5WzAeQ4?si=wWrmcd1ITlezo5JX&t=80). What you're seeing isn't subtype group layers or experience builder showing asset groups, it's just a collection of layers under a group layer with definition queries applied. They chose to do this using regular group layers, instead of subtype group layers, because the experience builder does not currently support subtype group layers, and they wanted to see their results separated out by asset group. Manually separating out your layers using definition queries is typically not recommended because of the performance cost (you have to query/render the same layer multiple times) but because it is only being done a handful of times this should still perform reasonably well. ... View more