Latest Contributions by MikeMillerGIS

‎05-16-2026

Easiest way to think about it, is the Asset Package is the complete representation of the Utility Network, but serialized or represented in a series of visible tables. Running Asset Package to GDB always creates a brand new Geodatabase. The tools take all the rows from the C_Association table and format them into the format that Import Association requires(csv). You can see these files in the AP_Workspace folder. Can you post the entire message from the GP tool?

‎05-15-2026

If it was not working for all the streetlight rows, I would expect an error message for each. I am going to add the def query to the error message so if we encounter this in the future, it would help us hunt down the suspect row.

‎05-15-2026

I take that back. Streetlight is the destination, which is what we support. I walked through the code and nothing stands out why it would not work. The logic queries the streetlight class and extracts the parent global ids from the relationship key field. My only guess is it is because the inputs are listed N times. Could one of them not have rows or a valid relationship? As a test, if you duplicate the relationship lookup key, make it unique for all streetlight subtypes, does the error message list them all, or just a subset? So try SupportStructureStreetlights1, SupportStructureStreetlights2, etc

‎05-15-2026

Hard to tell without a sample to test it, but I think the direction is wrong. The Streetlight is the destination in the relationship? If you set the association info on the support structure to the streetlight and not the streetlight to the structure, does that work?

‎05-13-2026

In the Utility Network properties page, in the tiers subnetwork definition, scroll all the way to the right. You can also use the Generate Schema Report tool and review it in there. You should see something like this:

‎05-12-2026

Phase Normal is not set up as the propagated value in the model. Phase Change is. Phase Change needs to be defined on the controllers and any place phase deviates.

‎05-12-2026

You can find the data dictionaries here - https://doc.arcgis.com/en/arcgis-solutions/latest/reference/introduction-to-electric-utility-network-foundation.htm#ESRI_SECTION1_7F90EBF29A6E451F837FF680AB23097A As for the circuit, what terminal did you connect the connector too? What terminal did you assign the controller info on?

‎05-07-2026

The table does not have to be in the service. I wonder if it has to deal with you do not have Exclude from Client Application checked. Try checking that so the rule is only run the database.

‎05-07-2026

How was the master street name table created? Is it registered with the GDB? Who is the owner of the table?

‎05-07-2026

Ok, That helps. The error is that the FeatureSetByName cannot find table. Can you move it all to a file geodatabase for testing to ensure the rule works? That would help eliminate variables with enterprise databases and permissions.

‎05-07-2026

Do you happen to have any other attribute rules? The error message does not match the code above.

‎05-07-2026

I do not know, I do not have access to the data so very hard to tell. Can you verify the name of the master street name table? Does you street have a street name of "Street Name"

‎05-07-2026

Try this. Also, when posting code, please use a code samples(Javascript works good for arcade). Makes it much easier to read if (IsEmpty($feature.FullStreetName)) { return true; } var addresserStreetName = Upper($feature.FullStreetName); var masterStreetName = FeatureSetByName($datastore, 'vwAddresserData_v2', ["FULLADDRESS"], false); var matches = Filter(masterStreetName, "UPPER(FULLADDRESS) = @addresserStreetName"); if (Count(matches) > 0) { return true; } return {"errorMessage": "The address " + addresserStreetName + " does not exist in the master Street table."};

‎05-06-2026

Add devices/junctions technically have terminals. If a terminal configuration was not applied, you need to set it to Single Terminal. Example:

‎05-06-2026

We model these locations as devices to simplify data conversion from existing datasets and to support ongoing editing and data maintenance. The device feature is configured as a container, allowing you to add unit-level details using WaterJunctionObject features. If a more detailed representation of a pump station or other facility is required, I recommend using structural containment through the Structure Boundary or Structure Junction features instead. For example, lets look at a Pump Stations. In this example, we are modeling three pumps. If we turn on Show Content, we can see that fitting and the valves turn on. So we are essentially modeling "Assemblies", but using the structure boundary instead of a domain Assembly feature.

Online Status	Online
Date Last Visited	Tuesday

My Ideas

Latest Contributions by MikeMillerGIS

Re: ERROR 160874: The utility network association already exists

Re: No association records found Streetlight key SupportStructureStreetlights

Re: No association records found Streetlight key SupportStructureStreetlights

Re: No association records found Streetlight key SupportStructureStreetlights

Re: Update Subnetwork not updating Isconnected and Subnetwork Name

Re: Update Subnetwork not updating Isconnected and Subnetwork Name

Re: Update Subnetwork not updating Isconnected and Subnetwork Name

Re: Create Street Name Validation

Re: Create Street Name Validation

Re: Create Street Name Validation

Re: Create Street Name Validation

Re: Create Street Name Validation

Re: Create Street Name Validation

Re: Junction-Junction Associations require to_terminal

Re: Utility Network – Why is “Station” modeled as a Device instead of an Assembly?

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

Re: Pipeline Isolation Subnetwork Confusion

Re: Published UN webmap showing coded domain value...

Re: 14 Million Associations - Best way to load to ...

Re: Water UN Data Cleanup

European Utility Network Community (UNC)