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; } } }

Exclude Copy Fields Not Honored When Using Create Migration Workspace UDMS 3.5.0

GISP00

Environment - Pro 3.6.2, UDMS 3.5.0

My Simple Data Mapping workbook has 81 fields configured in the Exclude Copy Field worksheet. After running Create Migration Workspace, the fields are copied to the Data Reference Workbooks in the Data Loading Workspace. See attached log and screenshots for confirmation.

The "sample fields copied PNG" file attached shows a filtered list for reference of this issue, but also note that all fields in the Exclude Copy Fields worksheet in are still copied to the Data Reference workbooks.

I also tried the UDMS 3.5.1 as well with same results.

CreateMigrationWorkspaceLog.txt

sample_flds_copied.png

ExcludeCopyFlds_screenshot.png

Trouver plus de publications taguées avec

Accepted answers

GISP00

@RobertKrisher I did indeed cause the issue. The Asset Package had the fields I was trying to exclude from copying. Problem solved by replacing the corrupted copy with a clean copy of the ArcFM UN Asset Package. Thank you for your assiatnce.

All comments

GISP00

@RobertKrisher I think I discovered the cause. I am using an Asset Package that already contains the fields I am trying to exclude. At some point I must of corrupted the ArcFM UN AP. I will run it again soon after resetting my Asset Packages.

GISP00

@RobertKrisher thank you for replying on a Sunday. I re-ran the Create Migration Workspace using a new project (to avoid using any cached data) and a new directory location for output to insure I am looking at the correct file. Same results, fields are copied even though "exclude copy fields" in simple data mapping is configured and Copy Fields is Unchecked.

New log file attached. For client's privacy I did rename some of the file paths in the logs. But critical parameter configurations are true.

For now I will use a script to delete the fields in the source and move on with my task. However, I would like to continue to explore a cause & resolution. I will be happy to share all data through email or another secure method.

ExcludeCopyFlds_screenshot2.png

CreateMigrationWorkSpace_Scratch2.txt

CreateMigrationWorkspace_screenshot2.png

RobertKrisher

The log you have attached shows the Copy Fields option unchecked, which means there shouldn't have been any fields added to the asset package when the migration workspace was created. This makes me wonder if you're looking at the wrong migration workspace. If you run the tool multiple times with the same output folder/name it will change the output name and location instead of overwriting the workspace.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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