Transfer utility network data from asset package or fgdb to enterprise geodatabase

Question

I deployed a UN v7 in an enterprise geodatabase 11.3 in the production system, and the data have no topology errors.

Now I need to transfer new utility network data (just data with attachment and association) stored in an AP or UN file geodatabase to update the enterprise geodatabase 11.3 that is in production. This UN contains data for a new municipality that is not included in the enterprise geodatabase. The two UNs have same schema.

The UN file geodatabase also includes attachments for UN classes and associations.

Which tool would be most useful to accomplish this? I am aware of the "Transfer Utility Network Data" tool (from  Utility-Data-Management-Support-Tools) , but it does not migrate attachments, for example, and I am not sure whether it can be used with an enterprise geodatabase.

MikeMillerGIS · Answer

I posted a pre-release of version of the UDMS for 3.5 that supports maintaining attachments in the Transfer UN Data tool - https://github.com/Esri/Utility-Data-Management-Support-Tools/issues/64

gpgisandsky · Answer

I need migrate data, attachments and associations. The option "manintain attachments" is active for default but the attachments have not been imported (data and association have been imported well). After I used append tool from AP to target UN using directly the attachment tables (from AP xxDevice__ATTACH-->UN xxDevice__ATTACH ) and the attachments have been imported well. I did these test using Asset Package to UN stored in a file geodatabase. May I execute  Transfer Utility Network Data directly on enterprise geodatabase? Why attachments are not imported using Transfer Utility Network Data tools (udms v.3.4.4,  Pro 3.3.7, UN version 7)?

RobertKrisher · Answer

If the asset package contains utility network features and attachments, and you just want to migrate the attachments, you will need to append the attachments directly. Be very careful to ensure that you don't double-load your network features. It is possible to load the same features with the same global ids multiple times, and it is painful to recover from this mistake. This can happen when you choose to preserve global ids during data loading.