Latest Contributions by RobertKrisher

@Brian_Laws while you can explicitly define editing templates in a specific map, the recommendation is to use shared editing templates because this allows an administrator to manage a single set of editing templates in the geodatabase then each web map can reference them. Think about the implications of realizing you need to override the default value on a particular attribute in certain editing templates. If you do everything exclusively in web map, that means you need to open and review each web map to try and find (then update) that template. If you store them in the geodatabase, then you edit it in one place and all the web maps benefit. ... View more

@kvincent there needs to be something done, and while it could be done manually it could just as easily be done through Python or Arcade (if you are proficient with those languages). The problem with doing all this work directly against the versioned data is that history is going to accumulate, and you don't have the degree of separation between your live network data and the historic of your asset registry. ... View more

Is there a reason why you need to put it on the hydrant itself instead of using a separate point class that represents the inspections? If you are setting/updating a flag on the hydrant (or any other feature) that represents its inspection status you're going to need to push multiple updates to each of those features every year (resetting the flag saying it needs to be inspecting, marking the feature as inspected, then updating the last inspected date). Because the UN data is versioned, all these edits are tracked and archived forever. A more sustainable approach for inspection is to manage the history, status, etc using separate tables. Not just for hydrants, but for any kind of asset you are performing preventative maintenance/inspections on (valves, pump, etc). It also solve the problem of what to do when a hydrant is abandoned or removed and you don't want to lose the history of the asset for liability reasons. ... View more

My experience has been that if the layer already has field properties explicitly defined and saved in the map (which it won't until you change something and save), the field will appear at the end of the layer's field properties. If the layer doesn't have field properties explicitly defined, then fields will appear in the same order as the feature service. One of the things I like to do for fun/paranoia is set up the Schema Report tool to run on a weekly basis in my major geodatabases, then I will periodically use the Compare Schema tool to check for any data model changes that may have been 'forgotten' to be communicated/documented. I will then go through and chase down who made the schema change (pro tip, check the GP metadata history) then make sure that these changes are accounted for in any of the relevant maps/services (do users in group X need to see this field? does it need to be highlighted? what order should it appear in?). ... View more

@strmside please log an issue as this may be specific to the data/configuration you have in your asset package. Mike is out of office right now, but my guess is that having sample data will help. I have some concerns about the data model I see in this spreadsheet (no field reuse, haven't paired back expanded model, etc) but I'm going to hope that's because you've had to regenerate your mapping sheets. Remember, if you implement the expanded model you need to make sure you remove anything you don't need (fields, asset types, etc) otherwise you will end up with a large, less performant model. If you plan on just adding your existing data model onto a foundation, start with the essentials model then just make sure that you're reusing fields (achorsize, structuresize, etc). ... View more

Creating database views isn't a viable option because the data is registered as versioned. However, in the past the way I've tackled this a few different ways. One way is to have the inspection information be a feature class, whose geometry is populated when a user clicks the hydrant they want to inspect. The other way is to create all the inspections ahead of time, with the geometries and status you want. This approach has the benefit of being able to symbolize the status in the map and provide a dashboard breaking down inspect, uninspected, and exceptions for the year. ... View more

I'm a little late to the part on this question, but I was looking for some other CP related info and I've found the Understanding Cathodic Protection article from @TomDeWitte to be very useful for answering these questions. ... View more

The requirements you have listed are common requirements for utility data in an enterprise GIS, and are not impacted one way or the other by the ArcGIS Utility network. Take care when designing considering your options for solving these requirements. As an example, hydrant inspection/maintenance history (including pressure tests) are usually stored in a separate asset management system so that it remains even after the asset has been retired or abandoned. Because features in the GIS are often deleted when retired, or moved to separate layers when abandoned, you should consider how you will handle the history if you decide to implement a solution that does not include an asset management system. ... View more

@gis_KIWI4 that's a pretty typical approach. The place where I've seen customers (mostly North American) model their substation (Transformer to Distribution Feeder) as a subnetwork is when they want to use the GIS to feed the substation internals in their OMS/ADMS. ... View more

ArcGIS Pro 3.7/ArcGIS Enterprise 12.1 is latest publicly available Network Management Release and not the release coming out later this year. But you may be referring to current as in the release of ArcGIS for the project you're currently on. ... View more

If you export the results of a trace using export subnetwork (or upstream/downstream trace) using ArcGIS Enterprise 12.1 and ArcGIS Pro 3.7 you will see an "include flow direction" option that will let you know the orientation of each line in the network with respect to the flow calculated by the subnetwork controller. See more here: What's new for ArcGIS Utility Network with the 2026 Network Management Release ... View more

I look forward to seeing this presentation, it looks like it's part of the Sustainable Land Cover Management with ArcGIS presentation on Thursday morning. One way that you can deal with working in areas with limited or no connectivity is to allow crews to take the data offline. This allows crews to work on the data locally instead of relying on cellular connectivity. Crews can then synchronize their data when they are in an area with improved cellular connectivity, or ideally when they have wireless connectivity in an office. ... View more

Ok, having talked to a few people internally about this I see what's happening. The FeaturesPosted web hook doesn't trigger whenever a version is posted, instead is uses the schedule associated with the web hook to identify all the features that have been modified in default since the last time the web hook was run. This means that it can include edits from multiple versions being posted (or edits made directly against default). While this has its own important use cases, it is not what you're looking for, and it explains why we can't include the version name. Having a web hook that includes the version name would require us to create a new EventTrigger that fires every time a version is posted (which is why the naming of the existing trigger is unfortunate). The upside is that you would get the version name, the downside is that you wouldn't have a way to detect other changes made to default (i.e. direct edits). ... View more