Latest Contributions by MikeMillerGIS

I would need the source and target database in a fgdb. Do not need the Geometric network. Also the data mapping spreadsheet.

If you can package up a repo case(schema only), I can look a look. Reviewing the source, it has something to do with the source to target mapping and subtypes. It should be looking at the subtype name. Do you have subtypes who description is a number?

I believe those are the only fields added. They can be deleted as they are only there to provide a link back to the source data.

You should focus on subtypes, removing them, will remove the asset types(domain codes) and all related UN properties. So set all items in the subtype section that you do not want to Always Remove

According to the sql, which is NOT (AssetGroup = 18 AND AssetType IN (0,301,302,305,306,309,310,311)), the config table is removing that item.

With a config table, it applies a sql query to exclude asset groups and types that are no longer valid in the target. If you run that query against your asset package(select by attribute), do you get any records? Also, you will see much faster times running locally. Running with source and result on a network share drastically slows down performance.

In the AP Workspace folder, can you share the log file? When you say delete, the data or schema?

I would run Asset Package To Geodatabase(File or Mobile gdb) and then the Error Analysis Tools(https://pro.arcgis.com/en/pro-app/latest/tool-reference/utility-networks/analyze-network-data.htm)

In the clone dialog, did you click Refresh?

I believe this behavior is based on https://en.wikipedia.org/wiki/DE-9IM

The standalone atbx will not be upgraded to 3.5 and only works in 3.3. The tools are part of ArcGIS Pro in 3.5. If you have the old toolbox in your project, you need to delete it. Pro could load this first, and when you try to use the 3.5 version, it will try to use the 3.3 version since it detected it first. That is why you are getting that errors. When upgrading to 3.5, make sure to delete the stand alone migration atbx.

Yes, that is the reason. Couple issues we have seen with them in the UN - Visualization: Many times, we want to see abandon assets separately. This has lead to duplicating the UN layers with def queries to remove/show abandon features. This is not a good practice and can cause issues with the UN tools. - Errors: abandoned features in the UN can still generate errors. - Offset/Snapping: the abandoned features still participate in the topo. So if you replace a pipe, but want to keep the old pipe, you need to move its Z so it does not conflict with the new pipe.

The pipe connection and/or manhole channel that the rule is creating requires a value for active volume. So you can either make the field nullable(and adjust the network attribute), or adjust the rule to include a value in the return edits. We could also define a default value on those subtypes in the data model. That might be the easier fix.

We prototyped an Attribute Rule that would move copy/move features to an abandon layer. You can try it out and see if it meets your needs. There is a GP tool in this toolbox to set up the attribute rules. https://esri.github.io/arcade-expressions/docs/3.3/AbandonRows.html https://github.com/Esri/arcade-expressions/tree/master/attribute-rules/attribute_assistant

‎09-29-2025

ArcGIS Online does not support hosting Utility Network layers. You must have ArcGIS Enterprise to publish the feature service.

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by MikeMillerGIS

Re: Create Migration Workspace error

Re: Create Migration Workspace error

Re: Migration Tool Output Schema

Re: Data Deleting When Applying Asset Package

Re: Data Deleting When Applying Asset Package

Re: Data Deleting When Applying Asset Package

Re: Data Deleting When Applying Asset Package

Re: Field Editing of Data in Asset Package

Re: UN Tools (ArcPro 3.5)

Re: Polylines touch and cross behaviour - Status changed to: Open

Re: Utility Network Tools update to 3.5.3

Re: Underground Asset Abandon Tools For Utility Network

Re: Attribute Rule failing on Manhole creation in Stormwater

Re: Underground Asset Abandon Tools For Utility Network

Re: Utility Network to AGOL without Enterprise

Re: Migration Tool Output Schema

Re: Field Editing of Data in Asset Package

Re: Utility Network Tools update to 3.5.3

Re: Underground Asset Abandon Tools For Utility Ne...

Re: unable to create UN 5 Utility Network using As...

European Utility Network Community (UNC)