Latest Contributions by SSMIC3038

One database can have one utility network with multiple domain networks within. Multiple utility networks on one database doesn't work, I'm assuming it's due to reserved naming conventions. To date I've never found any material from ESRI on how to create multiple domain networks within one utility network, which is odd because they promote this so much in their marketing. With quite a bit of effort I've managed to get multiple domain networks in a single utility network up and running, some literature from ESRI would be nice. I also have a couple of threads on this topic and they've never received a comment, so not much help available. ... View more

That's pretty impressive, are you referring to the new tools your working on or Randall's double mapping approach in the current model? ... View more

Wouldn't the result be 3 points stacked atop one another? Since the source manhole is seeding the 2 pipe connections and the new manhole. Actually, this got me thinking that there's probably a way in the source data to break lines a set distance (3m) from each manhole (buffer/clip??) which then creates geonet errors on the pipe ends, those errors could likely be isolated and used to seed the pipe connection in UN. The stub (3m) pipe segments could also likely be isolated and deleted. ... View more

I think your missing the distinction in my comment. The only way to create the service in a way that worked with validating edits was by adding only the utility network layer and letting ArcGIS Pro enforce adding the rest of the layers in the network. Adding the feature dataset would not recognize the Utility Network in such a way that allowed validation even though the UN was in the service and version management enabled, but by adding the UN layer itself, which then enforced adding the associated  layers, would it allow for a validation in the feature service. And I came across this resolution buried  in a thread somewhere. So, the resolution for this problem is - when creating a feature service with Utility Network add the Utility Network layer first and aceppt when ArcGIS Pro prompts to add the associated layers in the UN, then continue building the service. Don't add the feature dataset with the expectation that all the layers will work. At least in my case that is what resolved the problem (and whomever the oringinal thread belonged to as well), maybe its a bug, I dunno. ... View more

Works, thank you! ... View more

The project opens closed. Of course. Thank you, that resolved the problem. ... View more

Just want to voice support for this thread, I'm having the same challenges with sewer, water distribution and electric distribution models. The level of documentation on how the models work and the theory of "what should go where" is sorely lacking and patchy at best. ... View more

- topology enabled? - are there valid network rules for the features you are trying to connect? ... View more

Still trying to find a resolution to this - the feature services do have Version Management enabled but there are no actually topology error layers in the service. I can validate in the map service and topo errors are created but the feature service does not list any point, line or poly layers and the attribute table is not present. When I add the feature service to a web map the Utility Network layer is present but there is nothing to it, no point line or poly symbols, no attribute table. When I view the data directly in the database topo has been created, but I can't view the topo in a feature service. ArcGIS Enterprise v10.8.1 ... View more