Latest Contributions by RobertKrisher

‎08-23-2023

So many questions! All configurations are valid, and how you have this configured depends on your requirements. Updating subnetworks without eventing is more performant, but doesn't trigger geodatabase events like editor tracking and attribute rules. The reason why this is the default in the tools is because this was the original behavior that was implemented in the utility network, and the second mode was added later. When updating subnetworks in a named version without eventing there is the additional restriction of only being able to update subnetwork information for features that have already been modified in the version.

‎08-23-2023

If there isn't a source/sink to compare to, I'm not sure how the trace would be able to establish the directionality to say that something is upstream or downstream. However, what you can always do is take the condition barriers from your downstream trace and perform a connected trace. This will allow your trace to respect the same traversability conditions as your subnetwork trace without relying on a source. If you're going to be doing this often, consider making this a named trace configuration.

‎08-21-2023

What you're looking for is to identify the equipment that will act as subnetwork controllers, this is typically done by identifying a particular port on a device as being the head-end of a circuit (As opposed to a cable). If you haven't already, download the Communications Utility Network Foundation to see examples of how they've created the subnetwork controllers in their sample dataset.

‎08-21-2023

@DeepikaJain01 that's great news! You can find blogs about creating subnetworks over here: Managing Subnetworks with ArcGIS Utility Network. A little later this year we will also be posting several tutorials covering the content of the blogs.

‎08-17-2023

@robertopepato_bizpoke I recommend you reach out to @mmiller to review the logs from apply asset package to see which specific table it was failing on.

‎08-17-2023

You should only use the Change Asset Package Spatial Reference tool to reproject your asset package, using any other method will cause you to lose the contents of all the system tables in the original asset package. As long as you use the correct tool it will preserve all the original rules, configuration, and data of the original asset package. With regards to the 0000 globalids, if your source data had global ids you need to make sure that you have mapped them to that field. If your source data did not have global ids, you'll need to run a script to calculate a new global id for each row. I stole the following script from this community post: import uuid fc = 'TEST.russellpythonguidtest' rows = arcpy.UpdateCursor(fc) for row in rows: row.PYTHONGUID = '{' + str(uuid.uuid1()) + '}' rows.updateRow(row) https://community.esri.com/t5/geoprocessing-questions/write-guid-using-python/td-p/118035

‎08-16-2023

@FaisalAl-Yaseein the find subnetworks pane filters that list using the subnetwork lines in your map. Because you don't have a subnetwork line for this subnetwork, yet you need to go to the filter category of the find subnetworks pane and filter on the subnetworks table. This will show you the complete list of all subnetworks.

‎08-16-2023

Agree with @TobeyKane-Seitz 100%. You'll need to go back to your asset package and run the "Change Asset Package Spatial Reference" tool to put the data in the correct coordinate system. You can then stage/apply your asset package normally.

‎08-15-2023

@robertopepato_bizpoke Ok, this appears to be caused by bug BUG-000152404 and a specific attribute rule in the core asset package. @mmiller do you have a workaround for this issue for this version of the communications utility network foundation?

‎08-14-2023

I don't believe we expose it as such, but you can get the current schema generation from the utility network description (Utility Network properties—ArcGIS Pro | Documentation) then, depending on your pro client and ArcGIS Enterprise, determine whether you want to upgrade your utility network. Refer to the chart at the bottom of the dataset administration page for a table of version compatibility between schema generations, ArcGIS Pro, and ArcGIS Enterprise.

‎08-14-2023

That looks like a bug, so you should log an issue for it. What version of ArcGIS Pro are you using? What version of the Comms model is that?

‎08-10-2023

@SergueiSokolov When you do a copy/paste you have to do it at the feature dataset level. This will bring along everything in the feature dataset, all related objects, and the content & current state of the utility network. When you export/import you must re-enable the topology and update subnetworks in the target environment. When you copy/paste it will retain the current state of the system. The tradeoff is that export/import is able to more quickly transfer the data because of parallel processing.

‎08-10-2023

@MikeGoggin We're actually both right 😀. Copy/paste is the easiest way to transfer the data, but if you have a lot of data (especially a lot of associations) it's usually faster to use the asset package tools to export/stage/apply. One of the reasons why apply asset package is faster is because it will load data into the SDE environment using multiple threads, whereas the copy/paste is single-threaded.

‎08-10-2023

@neomapper John's approach will deploy an empty schema to your environment using a spatial reference from our sample dataset. Other items to consider: You should change the spatial reference of the asset package to the coordinate system of your organization using the "Change Asset Package Spatial Reference" tool, also in the Utility Network Package toolbox, before deploying If you're just looking to try out the model, the link John provided includes a file geodatabase that contains a standalone utility network that can be used without an SDE or ArcGIS Enterprise When you want to see your data in the utility network you should migrate your data into the asset package (With the updated spatial reference) then stage/deploy THAT asset package to SDE

‎08-10-2023

If you want to move an existing utility network to a new geodatabase (File, Enterprise, or otherwise) you can just copy and paste the feature dataset containing the utility network to the new database and it will move it, along with any related data.

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by RobertKrisher

Re: Utility Network & Eventing - required at all?

Re: What if you dont have a subnetwork in telco Utility Network and you still want to run Upstream and Downstream traces

Re: What if you dont have a subnetwork in telco Utility Network and you still want to run Upstream and Downstream traces

Re: Reproject Utility Network Issue

Re: Steps to deploy Communications Utility Network Foundation 1.4

Re: Reproject Utility Network Issue

Re: Issue Subnetworks not appear in find subnetwork in Utility Network

Re: Reproject Utility Network Issue

Re: Recommended way to deploy electric utility network foundation in ArcGIS Enterprise

Re: Is there a way to tell if an upgrade to your UNM is available

Re: Recommended way to deploy electric utility network foundation in ArcGIS Enterprise

Re: Recommended way to deploy electric utility network foundation in ArcGIS Enterprise

Re: Recommended way to deploy electric utility network foundation in ArcGIS Enterprise

Re: Recommendations on creating a sql database for the UPDM?

Re: Recommended way to deploy electric utility network foundation in ArcGIS Enterprise

Re: How to sync my Utility network geodatabase wit...

Re: Pre UN migration data cleanup workflows

Re: Best practices for managing and validating Uti...

Re: Pre UN migration data cleanup workflows

Re: Can one web map hold two separate utility netw...

European Utility Network Community (UNC)

APAC Utilities Community of Practice