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

Load Data Using Workspace Error 000549

auustinreeves

Hello, I am having a hard time with the Load Data Using Workspace tool right now. This is a redo of what was a successful data load into the Water Expanded Solution about a month ago using the exact same source data.

Create Simple Data Mapping works fine. Create Migration Workspace works fine. When I run the Load Data Using Workspace, I get the following errors for every feature in my migration:

I have tried making a fresh download of the solution's atbx, the "untools" atbx, and the Asset Package.

Only things modified for the Asset Package are the Change Asset Package Spatial Reference tool, one B_Rules addition, a few Subtype default changes, and removal of the Asset Groups and associated relate classes/tables for those not needed.

Then, the Load Data Using Workspace tool shows the error shown above.

I work in a virtual environment and have noticed that the tool's output is going to my C:\Users "vault" filepath (put short, the virtual machine's file connection to the "V" drive). Whereas the source data is coming from my "V" drive directly... We did just switch to this VDI setup, and I'm curious if anyone has experienced similar issues with other things? I'm still very green with virtual environment file management..

Thanks!

Vind meer berichten getagd met

Accepted answers

MikeMillerGIS

Thanks, that helps narrow down when the change occurred.

I can repo with just using append also. We believe it is caused by the attachment relationship. The WaterDevice has a GlobalID field of type guid, which is used by that attachment relationship. If you delete the attachment relationship and leave Preserve Global ID on, the data load completes.

For now, In the Data Loading Workbook, turn off Preserver Global ID. It is not needed as the Asset Package uses a Guid field for global ID and field mapping will preserve them for you.

All comments

auustinreeves

I finally had time this afternoon to jump back on this and try it out.

It works! Thank you so much, Mike and the esri UN team. You guys rock!

MikeMillerGIS

Thanks, that helps narrow down when the change occurred.

For now, In the Data Loading Workbook, turn off Preserver Global ID. It is not needed as the Asset Package uses a Guid field for global ID and field mapping will preserve them for you.

auustinreeves

I'm on 3.6.1 - fresh install as of two days ago (due to the new VDI).

MikeMillerGIS

What version of ArcGIS Pro are you on? This is due to PreserveGlobalID being set to true in the Workbook. Turn it off for now. We are looking into why this matters and are unsure at the moment.

auustinreeves

Sure thing - what is the easiest method for you to receive? Should I direct msg you?

MikeMillerGIS

I am not sure, is there any way you can package it up? I can run through the process in debug mode and see what is going.

auustinreeves

Saw that as well, and everything is well contained in the Service Territory. Source data and Asset Package are in the same CS. I also tried repair geometry on all source features.

auustinreeves

*I also tested adding the Created/Edited User/Date attributes to the mapping table as well (along with OBJECTID) to no avail.

MikeMillerGIS

Interesting, looking up 594, it has to deal with spatial extent. Do you have features outside the service territory of the UN or the extent of your data?

https://pro.arcgis.com/en/pro-app/3.4/tool-reference/tool-errors-and-warnings/001001-010000/tool-errors-and-warnings-00576-00600-000594.htm

auustinreeves

Running the Update Data Loading Workspace Schema added some association/tier/subnetwork fields to the mapping table, as shown below (everything after the "symbolrotation" field). I've included my source's fields as well for reference.

Am I missing something? The only field that is not in the mapping, but is in my source, is OBJECTID. This was not added when running the update schema tool (I added it manually for a test, but got the same result). Still getting the error on Load Data.

MikeMillerGIS

If you review the field mapping of hydrant to WaterDevice, can you make sure all the fields exist in both the source and target?

If you run Update Data Loading Workspace Schema, does it change any anything in the mapping sheet?

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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