Latest Contributions by RobertKrisher

‎03-27-2026

You need to connect to a machine that has a better (i.e. lower latency) connection to your SDE environment. Even if you use something like an asset package to redeploy the database, you're going to run into the same problem with latency. If you don't have a good, local connection to your SDE you should have a machine co-located with your SDE infrastructure that has ArcGIS Pro installed for administrative purposes. Some customers choose to have a dedicated machine, others will install ArcGIS Pro on one of the machines in their ArcGIS Enterprise deployment.

‎03-26-2026

@PierreloupDucroix index issue aside ... I had some issues getting the Append to work properly, until I read the doc more closely and realized that the Preserve Global ID option will only be respected on append (at the REST level) when defining a Matching Field, which places the tool in an Upsert Mode.

‎03-25-2026

Yes, curves are supported by the utility network and ArcGIS Pro.

‎03-25-2026

If you create a utility network and register it as versioned you should get a unique index. You should then be able to run the append tool, with the preserve global id option, against a branch versioned service into a named version. I'm not sure what the add tool is, or whether you meant the append tool.

‎03-25-2026

@PierreloupDucroix I was not suggesting using the add index tool to create your own unique index on this field. I was showing how the OOTB field should look once the enterprise data is versioned. I recommend you log a case with support about the append tool not working on branch versioned data.

‎03-25-2026

Also, instead of using Asset Group codes or Asset Type codes for your filters, consider using a network category. Asset groups/type codes are not guaranteed to be unique, and using a network category allows you to exclude/include multiple asset groups/types with a single category. It also makes the filter easier to understand. Saying you're excluding asset group 12 doesn't mean much, but saying you're excluding something like "cathodic equipment" or "high voltage" does.

‎03-24-2026

How are you loading the data? The unique index for archiving is unique because it includes the GDB_From_Date. Once you load data into the enterprise and register it as versioned you should see that the table has a unique index on the global id field in the UI. If you look at the database, you should see that the index includes the gdb_branch_id and gdb_from_date columns.

‎03-24-2026

If you put all the charateristics for the score on a single layer, you can use the Calculate Composite Index tool to create a weighted score. Here are some articles that give an overview of things to consider for weights and process: Enterprise GIS and Infrastructure Management Calculating the Consequence of Failure Infrastructure Maintenance and the Geographic Approach If you do end up taking the composite index approach, you can find quite a few articles and tutorials online form Esri on how to use them.

‎03-24-2026

You should set the TerminalConfiguration field to be Default, not All. This is the preferred default value. This is important when the device has more than two terminals, since you only want the default valid paths to be used. Similarly, you should default the FlowDirection field to the default value of "With Digitized". These are the default values expected by the utility network, but when you build a data migration you need to make sure you are providing the appropriate default values for the migrated data for both system and non-system fields.

‎03-24-2026

The ObjectID and GlobalIDs field cannot be unique, at a database level, on a class that uses versioning or archiving. This is because these values will appear in the same table multiple times for each edit made to the feature (in default and in versions).

‎03-23-2026

@KymBeard07 If you let support know about the bug number I've mentioned above, they should be able to get you more information.

‎03-23-2026

After you upgraded to V7 the flowdirection attribute should be populated with the default value (with digitized direction). If not, you can use field calculate. The flow direction network attribute isn't really used by electric networks.

‎03-21-2026

Please log a case with support. There were several bugs with isolation traces that match the behavior you are seeing (one of them is BUG-000179357) and they can help determine what the options are. The fix for these bugs has been backported as far back as 11.1. But since you're on 10.9.1, that may limit your available options. If you were to upgrade to 11.1 patch 5, 11.3 patch 2, or 11.5 patch 2 this issue would be fixed.

‎03-20-2026

You may be able to get more details about what is happening by looking at the HTTP request/response in a debugger or in the server logs. If that doesn't help, or you aren't comfortable with those steps, please log a case with support on the issue. They can help you identify what is going wrong.

‎03-20-2026

No, the videos are not published anywhere.

Online Status	Online
Date Last Visited	yesterday

My Ideas

Latest Contributions by RobertKrisher

Re: Migrating a UN that exists in a Mobile GDB to SDE

Re: Creating a Utility Network creates a non unique index on globalid

Re: Curves in the Utility Network

Re: Creating a Utility Network creates a non unique index on globalid

Re: Creating a Utility Network creates a non unique index on globalid

Re: Excluding Features from Field Calculation in Batch Trace?

Re: Creating a Utility Network creates a non unique index on globalid

Re: Sewer Pipe Inspection Reports -> Condition Layer

Re: Terminal Configuration and Flow Direction

Re: Creating a Utility Network creates a non unique index on globalid

Re: Isolation Trace completed with warnings in large subnetworks

Re: Issue with FLOWDIRECTION being automatically added as network attribute to electric UN

Re: Isolation Trace completed with warnings in large subnetworks

Re: Error executing trace configuration in web map (Utility Network)

Re: Esri Water - Utility Network Working Group

Re: Valid paths not routing upstream trace correct...

Re: Feedback on the Prune Branch History Tool

Re: Edit Widget: Create Feature function not displ...

Re: Asset Package - Change Asset Type Domain for a...

Re: Feedback on the Prune Branch History Tool

European Utility Network Community (UNC)

APAC Utilities Community of Practice