Latest Contributions by RobertKrisher

Inserting, updating, and deleting data directly using SQL is possible but is not recommended due to its complexity and risk especially when there is a controller dataset involved (topology, parcel fabric, utility network etc). The recommended, safe way to perform these updates is to make use of one an API (Python, .NET, REST, etc) that will manage the edits to the archive as well as ensure we maintain integrity with the controller dataset. As an example, if you insert a new feature into a topology using SQL the row will be created in the database, but no dirty area will be created. This means that the topology will not be able to validate the feature. For controller datasets that perform tracing the problem is significantly worse, because this means the feature will not be incorporated into the network index. Also, if you are making updates to features that affect the state of the network you will end up in a similar situation, with edits being made to features with no means to get them reflected in the network index. If you make the same edit using our API, we will ensure that in addition to performing the requested edits we are also properly managing any system fields. If you find out later that you have made a mistake that affects your topology, and try to log a case with support, they will be unable to help you because your use of SQL instead of the use of the APIs. ... View more

There is a dedicated learning series to migrating data to the utility network that includes links to many articles, tutorials, videos, and other important information that can help you on your learning journey. And I strongly second what @gis_KIWI4 said, reach out to this community whenever you have questions. ... View more

@gis_KIWI4 I would specifically say that they are coincident on the x/y plane, but because the utility network is 3d they won't be connected unless the tap/main/service all have the same x/y/z coordinate. ... View more

If you are just doing a local proof of concept of the utility network, have you considered just using a file geodatabase or mobile geodatabase? The Apply Asset Package to Geodatabase tool makes creating a local geodatabase for doing a proof of concept easy. ... View more

@FinnSwann The next meeting is going to be happening in February right? ... View more

@ahargreaves_FW Its hard to say based on the screenshot, please reach out to support so they can take a look at what's going on. ... View more

@ahargreaves_FW Pull the data into your map from feature services. Click Add Data, select Subtype Group layer, browse to your feature service, and select your corresponding layers. You can find an architecture diagram of this approach in this article: Understanding the Differences Between Utility Network Maps If you want examples of how to use/configure subtype group layers, check out this article: Configure a map using the ArcGIS Utility Network ... View more

@CarlVon_Stetten1 if you are not interested in retaining history in your geodatabase (across ALL branch versioned classes) you can unregister your data as versioned to lose all history and outstanding versions. One reason why your subnetwork line is so large is that you likely have included your laterals as asset types for your aggregated subnetwork line in your subnetwork definitions. This means that every time your update subnetworks you are creating a new copy of every main AND lateral in your system. I would advise you to only represent the mains in your subnetwork in your aggregated lines for both storage and performance reason. Including laterals in your subnetwork line makes the layer draw slowly, since you are having to draw every line in your system. Because you have a hierarchical network this means when you draw your subnetwork line layer you are effectively drawing every main and lateral in your database multiple times. ... View more

@CarlVon_Stetten1 If you check the cp traceability field in your data again, has it become null again? There is an attribute rule that is responsible for calculating that value, and I suspect that when you're adding these tiers and their new fields, that the rule is being triggered when the subnetwork name is set to 'Unknown'. The rule should return a 0, 1, or 2, but its possible with the modifications you've made to your model its returning a null value because something is exiting early. ... View more

Please log a case with support on this to investigate further. Do you have copies of your database from before you made these changes? If you were just adding tier groups/tiers and setting subnetwork definitions it shouldn't cause these problems. What could have caused this problem is if you had made changes to your network attributes or network attribute assignment. How the field is configured (to allow nulls) and how the network attribute is configured (to not allow nulls) are actually separate items. The interesting this is we don't allow you to assign a non-nullable network attribute to a nullable field, so that shouldn't have been possible. Changing the domain assignment shouldn't have affected anything, but calculating all the fields to be not null is what should have fixed the issue. ... View more

Not off the top of my head, although since you're working in an Enterprise environment what you're really hoping for is an 11.3 patch. Reach out to your account manager about this issue and they should be able to go through proper channels to come up with an estimated window. ... View more

@jtmathwig You should contact support for those issues. There is at least one known bug with isolation traces where placing the start location and barrier on the same line, which can produce incorrect results. ... View more