nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I migrate non-UN layers into ArcGIS Utility Network using Data Loading tools?

CuriousDaus

I'm currently learning how to load data into ArcGIS Utility Network using Esri data loading tools, Utility Network Foundations, and Utility Network Package Tools as per this tutorial . So far I've successfully migrated the Utility Network layers like pipeline, pump, valve etc. What about standalone non-UN layers/feature classes from the source database? For example: dam, spot height, water bodies & district boundaries.

One method that I can think of is using Append to migrate these non-UN layers/feature classes.

Najděte více příspěvků označených jako

Accepted answers

CuriousDaus

You're right. The tools can be used to handle any feature classes. We can just ignore the data validation error in the excel file and run the tools. For non-UN feature classes, I just assign the same name (source class) to the target class as per screenshot that I showed in previous reply.

BogdanHristozov

ESRI Data Loading Tools are designed to handle any feature classes, not just UN data. By doing so you can use the same pipeline: one workflow to migrate all your data. Apply data transformations, expressions, conversions, validate, etc.

Target feature classes must be created in the asset package prior of running the data migration.

All comments

CuriousDaus

The migration is an iterative process where records from non-UN Layers will be migrated from time to time. In the DataMapping excel file, I tried to assign the name of target class similar to the source class. But there was a data validation error because the names weren't in the Target Class dropdown list. I've provided a screenshot to show how I mapped the non-UN layers in the DataMapping excel file. The feature classes are in the asset package.

Screenshot 2026-04-02 082903.png

CuriousDaus

The migration is an iterative process where records from non-UN Layers will be migrated from time to time. I suppose ModelBuilder with task scheduler will suffice?

BogdanHristozov

Target feature classes must be created in the asset package prior of running the data migration.

MikeMillerGIS

You can just copy those classes as is. No need to migrate them.

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.