You may skip this step if... you do not have CU data in your geodatabase.
The Migrate Data tab allows you to run the Upgrade Compatible Units tool, which copies the CUs in your geodatabase from the existing (blob) format then inserts them into the tables created by the Update Schema tool. The data is copied — not moved. All existing tools work as they were designed.
Other tabs in the CU Administration tool contain tools that rely on the data in these tables. If they are not populated, these tools (e.g., Manage CUs) will not function properly.
Favorites created with features (rather than CUs) are not copied by this tool nor impacted in any way. You can continue to manage favorites using the ArcFM Solution Favorites Manager in ArcCatalog.
Any CU defining attributes (CUDAs) with null field values are not migrated from the existing (blob) format to the CU Filter tables. These dropped CUDAs are visible in the event log.
If the migration encounters duplicate CUDAs on a feature, it uses the last value provided. This information is also available in the event log. If multiple CUDAs on a single CU have the same name, they are considered duplicates. This information is also added to the event log.
To migrate your data into the new table structure, follow the steps outlined below.
- Ensure you are logged into the geodatabase as the owner of the system tables.
- Click the Upgrade Compatible Units button.
- When the upgrade is complete, the Migrate Data tab displays
a list of duplicate CUs it encountered during the migration.TIP: Duplicate CUs
The Migrate Data tool prevents the creation of duplicate CUs by creating a unique identifier for each CU during the upgrade. This unique identifier is a combination of a CU's WMS Code, subtype, and table name. As you see in the image below, any duplicated CUs that the tool finds are listed in the Migrate Data dialog, but only one copy is migrated. Data from the first CU encountered is used for the values inserted into the MM_CU_LIBRARY table. It is possible for a duplicate of a CU to have different values. CU Referencing synchronizes these differences to the values of the CU inserted into the MM_CU_LIBRARY. Synchronization is covered in the section below.
Persist CU Referencing Changes
The following steps outline how to review the values of duplicate CUs and persist any changes.
- All duplicate CUs listed in the Migrate Data tab should be reviewed to ensure that the MM_CU_LIBRARY has the correct data for them. Duplicate CU lists are not logged, so screen captures of them must be taken. It is okay to rerun Upgrade Compatible Units to refresh a list.
- Search for each of the duplicate CUs with the Compatible Units Administration tool and edit them as needed. The edited values are used to update all of the duplicate favorites that use this CU.
- When you are finished editing, click Save.
- Click the red X at the upper right of the Compatible Units
Administration tool to exit. In the Synchronize CU changes dialog,
click Yes. Ater clicking Yes, every CU Favorite is visited and updated
with the values from its corresponding CU in MM_CU_LIBRARY. If a CU
associated with a CU Favorite is not found in MM_CU_LIBRARY, warnings
are written to the event log.
The following data is updated for each CU Favorite:
Available Work Functions
CU Defining Attributes (CUDAs)
Units of Measure
Extended Data values are not updated. If a CU is contained in a favorite, you can either edit the CU’s Extended Data values or delete the CU and re-add it to get the updated Extended Data values. CUs that are not contained in favorites need to be deleted and re-added for their Extended Data values to be updated.