topic Re: Related record data loading strategies? in Water Utilities Questions

Related record data loading strategies?

Anonymous User — Tue, 12 May 2020 20:46:27 GMT

Does anyone have any best practice strategies for loading existing related tables (e.g. hydrant inspections, valve inspections) to the utility network schema? We have existing GlobalID-based relationship classes.

Any ideas would be appreciated.

EDIT:

With regards to Esri's Data Loading Tools... the tools include mapping of tables but maintaining related records is not mentioned in the documentation. Is it possible to migrate related tables using the Data Loading Tools?

Re: Related record data loading strategies?

RobertKrisher — Wed, 13 May 2020 22:23:03 GMT

Matt,

If the relationship is created on a GlobalID or user generated key then the process is very simple because the primary/foreign keys will be maintained through the conversion. If you're looking to convert relationships (or attachments) which use object id relationships, you'll likely want to add globalids to your source data ahead of the conversion (maybe even now?) and use a python script to map your old object ids to their global ids, then when you recreate the relationships just use the global ids instead. You'll likely want to do this anyways since globalid relationships will allow you to take your data offline.

Re: Related record data loading strategies?

Anonymous User — Thu, 14 May 2020 13:56:25 GMT

Ok, I'm working with the Water Distribution Utility Network Foundation (WDUNF) asset package. I am attempting to load a subset of my data into a file geodatabase with the applied WDUNF schema using Esri's Data Loading Tools. In my data mapping Excel workbook for my hydrants, I mapped the TargetField GLOBALID to the global ID field of my hydrants. Then I ran the Execute Data Load tool. The GLOBALID field in the target dataset does not match the global ID of the source hydrants.

I agree, it should be simple, however, I am not finding that to be the case. Could you provide an explanation of your process?

Re: Related record data loading strategies?

MikeMillerGIS — Thu, 14 May 2020 14:05:45 GMT

If you add a guid field to your hydrants and calc the globalids to it, then use that guid field to map to globalid, does that work?

Re: Related record data loading strategies?

RobertKrisher — Thu, 14 May 2020 14:31:05 GMT

Matt,

You shouldn't need to play any shell games with adding extra fields or calculating new global ids. I just ran the process end to end on my data. If your data already has a GlobalID column (a column with the GLOBALID data type, which it looks like it does) you should map your data to the "GLOBALID" field.

Then after running your data loading workspace the global id from your source feature will appear in the global id field on your new in feature:

If your data doesn't already have a GlobalID field you should be able to add one using Esris "Add Global ID" tool:

Re: Related record data loading strategies?

Anonymous User — Thu, 14 May 2020 14:34:53 GMT

No, that did not work.

Re: Related record data loading strategies?

RobertKrisher — Thu, 14 May 2020 14:39:43 GMT

Matt,

Can you show us the field data types for your source table as well as sample values for a single row for the globalid and globalid_1 columns?

Re: Related record data loading strategies?

Anonymous User — Thu, 14 May 2020 14:50:36 GMT

Re: Related record data loading strategies?

RobertKrisher — Thu, 14 May 2020 14:54:26 GMT

Matt,

For kicks try making the field mapping all uppercase ( !GLOBALID_1! ), then try running it through and show us what comes across in the "GLOBALID" field of the converted feature.

Re: Related record data loading strategies?

Anonymous User — Thu, 14 May 2020 15:13:41 GMT

Nope. Did not work.

Re: Related record data loading strategies?

RobertKrisher — Thu, 14 May 2020 15:22:48 GMT

Matt,

I'm gonna have to go dark for the rest of the day, but I'm wondering if there is something up with your asset package (potentially an older version of the model?). Check out my screenshots from earlier in the morning and you'll see that the "globalid" field in the target asset packaqge should be a guid data type and not a globalid data type, this is what allows the data loading workspace to bring your source globalid into the asset package. in your asset package your globalid field is a globalid data type, which means the data loading workspace cannot populate it. I would recommend you download and use the latest Esri Asset Package ( Water Distribution Utility Network Foundation | ArcGIS Solutions for Water ), as the asset package included in the sample data loading workspace appears to be using an older model that doesn't allow for carrying over globalids.

Note: there may be some adjustments you need to make to your data loading workspace if there are some model changes between releases. I did have to make a few changes, but I believe all of mine were related to source data issues.

Once you have global ids coming across, then getting your related records over should be (relatively) simple. As simple as anything that involves GIS and python can be expected to be.

Re: Related record data loading strategies?

Anonymous User — Thu, 14 May 2020 19:21:07 GMT

I was doing it wrong. I was trying to load my data using the DLT into a file geodatabase with the asset package applied and not the asset package itself. Ugh. Getting tripped up early in this new world.

Reading your response pointed me in the right direction. Thanks!!