I am looking for an example of using an attributed relationship to create associations in the simple data mapping workbook. They are globalid based and I have tried using either the Associations tab or writing to the c_associations table in the Data Mapping worksheet. Neither of these methods work for me. Using search by distance works, and I assume finding another way to populate the c-associations table will work. But I was wondering if I am missing something about being able to map the relationships direction using the Simple Data Mapping workbook and Create Migration Workspace.
Solved! Go to Solution.
Structural and containment. This is the method I am working on now, just thought fewer steps would be nice, as there alludes to this potential with the simple mapping method.
@strmside - Have you had a chance to look at this article?
https://www.esri.com/arcgis-blog/products/utility-network/data-management/load-data-into-a-utility-n...
We used the import Associations Tool Post go-live. In doing so we had to create a GlobalID mapping of the devices/junctions to structures outside of ArcGIS (we used FME) and then just the tool to import the associations in.
Yes, thank you. I was curious what this looks like.... "If the relationship between classes is an attributed or many-to-many relationship create a mapping using the attributed relationship as the target class instead of the destination of the relationship." My interpretation/attempts have not worked.
What type of association are you trying to achieve? You can load the primary and foreign keys into the from and to global IDs of the c_assocation table and set the association type, then run the Sync C tables (https://esri.github.io/Utility-Data-Management-Support-Tools/docs/3.1/SyncAssetPackageDataTables.htm...) tool to set their Asset Groups/Types.
Structural and containment. This is the method I am working on now, just thought fewer steps would be nice, as there alludes to this potential with the simple mapping method.
During migration, depending on order, we do not know the Asset Group/Type of the feature, so it is really hard to calc that in the data loading process. That is why it is best to have the Data Loading move the data, then run tools to sync the values in the C tables so they align to the records and how they were mapped/transferred.