Exporting to Asset Packages: Global ID vs Guid data type confusion

Andy_Morgan — Mon, 08 Apr 2024 20:40:38 GMT

What's the proper way to handle GlobalID fields when taking a brand new utility network and exporting to an asset package? I'm trying to put together a checklist for creating and applying packages to build a UN with both a Water and Sewer domain network, and I'll be going through the entire routine from start to end more than a few times between our development, test and production environments.

Here's the somewhat cumbersome workaround I've put together in order to avoid creating an unwanted "GlobalID_1" field in each standalone table or UN feature class.

After Create Utility Network and Add Domain Network (for Water and Sewer):

“Export Asset Package” to create an asset package using the empty utility network as input
Delete the “GlobalID” field (Data Type = Guid) if it exists in any standalone tables and reference classes (used in my attribute rules):

This includes Edge Object tables, Junction Object tables and UN feature classes ("SewerAssembly", "SewerDevice"....etc.)

Select tables and dataset, Manage -> ☑ Global IDs

or use "Add Global IDs" tool

If I don't do this, when I go to add attribute rules to my feature classes in the asset package it errors out saying must have Global IDs enabled.

And if I were to skip the steps for deleting Guid data type "GlobalID" fields then it creates GlobalID_1 which messes everything up. Surely I'm not understanding something fundamental and this isn't something everyone does each time...?

Re: Exporting to Asset Packages: Global ID vs Guid data type confusion

PaulLeBlanc1 — Mon, 08 Apr 2024 21:12:53 GMT

Attribute rules in the asset package are stored in a side table (B_AttributeRules). See https://doc.arcgis.com/en/arcgis-solutions/latest/tool-reference/utility-network-package/pdf/Utility%20Network%20Package_Asset%20Package%20Reference.pdf

Since it's much more convenient to use design view or geoprocessing to author attribute rules, it's a good idea to configure your attribute rules against the deployed utility network, not the asset package.

The GlobalID field in the asset package is a GUID so that the values can be maintained.

topic Re: Exporting to Asset Packages: Global ID vs Guid data type confusion in ArcGIS Utility Network Questions

Exporting to Asset Packages: Global ID vs Guid data type confusion

Re: Exporting to Asset Packages: Global ID vs Guid data type confusion