Example for Mapping Table in Data Mapping.xlsx

[Brian_Laws]

I am just beginning the migration of our Sanitary Sewer network to the Utility Network using the Sewer Utility Network Expanded Foundation solution V2.2.  I have created my Simple Data Mapping spreadsheet (Data Mapping.xlsx) and have filled out most of it.  I have completed the Data Mapping, Associations, and Exclude Copy Fields sheets, but am having a hard time understanding the Mapping Table sheet.  I've read the Info sheet regarding the Mapping Table but cant really make heads or tails of what I'm supposed to do in there.  I've seen a couple of tutorials on filling out this Data Mapping spreadsheet and none of them have any examples of what to do on this sheet.  Are there any examples of how to fill this sheet out that I haven't found?

[PatrickGCowan · Accepted solution]

The Mapping Table is used during the Create Migration Workspace step of the process where it generates a Data Loading Workspace. It is the mapping table that is used by Data Loading tools when doing field and coded value domain description matches and blocks. It is optional for this process, but can help you improve field and domain description matches, which reduces manual work that needs to be done. 

For example, if I enter the below line into the mapping table, any time that the fields FACILITYID and assetid are found to be an exact match between a source and target dataset, the fields will be matched in the output data loading workspace. If no match table were to be supplied, these two fields would not match because the names are not similar, and they would have to be manually matched.

This help page gives you some information on how the mapping table in the Data Loading toolset is used.

Data Loading - Mapping Table 

[Brian_Laws]

Awesome, thanks Patrick that was exactly what I was looking for!

[KathleenBallew]

Is there a more detailed tutorial on how to create and use a data mapping table? I'm not familiar with this level of programming and I have data where some fields match- like asset type- but in the agol solution the domains are coded with numbers and a drop down menu and in our existing data we used a text domain type.

I'm trying out this catch basin inspection solution for the first time and have been running into issues loading our data in a way that will be useful and not create more work/reinventing the wheel.