Latest Contributions by RobertKrisher

I have not seen this done in a utility network before, but I have seen companies create geospatial models for the "vertical assets" in their treatment plants that could be used to create a utility network. ... View more

Let's pick up this discussion over in main thread where you posted this ... https://community.esri.com/t5/arcgis-utility-network-questions/treatment-plant/m-p/1275976#M2461 ... View more

The views or materialized views I have included in that blog are going to be your best way of capturing this information. The main consideration for the materialized views in THIS use case is going to be performance. The materialized views will be faster for reporting purposes. Period. If you don't want the overhead of creating materialized views AND are willing to let your reports take a little longer to generate, use regular views. ... View more

I apologize if the blog didn't properly convey the design and intention of this, I will attempt to address your questions here. The materialized view is meant to act as a stand-in for the standard view, this is not to provide additional filtering, but because of the following two reasons: Evaluating the branch version query for all rows in your database is an expensive operation, so you don't want it evaluated for the entire database any time a user runs a report! Because data is edited throughout the day, there may be dependencies between your branch version data and other system tables / processes. Materializing the view ensure that your views + reports are always consistent and are unaffected by the edits that occur throughout the day. t0_ isn't a temporary file that is persisted anywhere, its a common table expression. While you could write a query that doesn't make use of a common table expression in Postgres, our testing has found that using a common table expression in Postgres allows for the planner to create more effective plans that execute in less time that the same queries that don't make use of common table expressions. ... View more

Thanks, I'll mark this as the solution you took. You should check out the Version Management role in a lower environment if you haven't already, it will allow you (as an admin) or any other super users to make changes to default while it is protected. This saves you the trouble of having to remember to run alter version to switch the version between protected / public when making schema changes. I would say it also means that you can post changes using your normal account, but you appear to already have a process in place for handling posting to your protected default. ... View more

If that is the case, try assigning the version management role to yourself and you should be able to get past this issue. See this blog or the online help if you want more info about this role. ... View more

Yes, an edge object can contain a domain line feature. A common example of this is that a conduit (Structure Edge Object), contained by a conduit system (Structure Line), can contain a Conductor (Electric Line). Mike's point on locatibility is important, so you'd either want your edge object to be contained in or connected to a spatial object. You can find the full matrix of what is allowed for connectivity, attachment, and containment associations on this page: https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/feature-restrictions.htm . ... View more

Mike,   The fields button lists all the fields for the feature class. If you want something like the online data dictionary that has aliases and visibility at the subtype level you will need to use the "Map Field Properties' button on a map that has been configured with subtype group layers that reflect the subtype settings you want. In the example below I've exported the map field properties from the water distribution utility network foundation utility network editor display and filtered the field properties to just show the values for hydrants.   ... View more

You can find an add-in in this thread that allows you to export your utility network properties to csv files to produce reports: https://community.esri.com/t5/arcgis-utility-network-blog/utility-network-properties-extractor/ba-p/1056201 ... View more

I recommend you log a case with support for this issue. ... View more

The online help that you mentioned shows how a customer would implement tier groups if they wanted to separate their hierarchical subnetworks into different tier groups. The example you have referenced in the help is for a gas model which is quite different from water. If you want examples of how to configure the utility network for specific industries I recommend you check out the ArcGIS Solutions gallery.  You can find example data models and configurations (called Utility Network Foundations) that you can download and review to answer questions like this. If you have any questions specific to data modelling, I recommend you reach out to the ArcGIS Solutions team as they are actively engaged with customers all over the world in creating these sample models. ... View more

This sounds like it may be related to validate consistency and dirty area management. You can read more about this topic here: https://www.esri.com/arcgis-blog/products/utility-network/data-management/dirty-area-management-with-the-utility-network/ Anthony is correct in that both systems will create a dirty area whenever a network attribute is edited. If you are receiving an error in EB but not in Pro, then the most likely scenario is that your Pro Trace configuration is not validating consistency but the name trace configuration configured for your web map is validating consistency. The Validate Consistency option will throw an error when a dirty area is encountered during tracing, which prevents in consistent trace results. In the case you outlined above, even though Pro isn't throwing an error it will not respect the change in the network attribute until the edit is validated. ... View more