Export/Import the Sample Data Model Schema

At this point, your geodatabase only has the ArcFM System Tables. It does not have the feature classes or object tables that represent the fiber features, nor does it have the relationships that coordinate those features and tables, or the geometric network. In these steps, you export the schema from the sample data model and then import it into your new geodatabase.
  1. In ArcCatalog, locate the Minerville sample geodatabase.
  2. Expand it to view its contents.

  3. Notice the sample data includes datasets for all ArcFM products. For this reason, you perform the export from the FiberDataset level, not the geodatabase level (otherwise, you get the schema for other industries and products).
    IMPORTANT:

    In the sample data, there is an existing relationship between fiber optic cables and conduit. This is included as a part of the sample data for Conduit Manager. If you are focused on importing the fiber schema alone, we recommend you delete this relationship first. If you do not delete the relationship, all other features in the electric and conduit dataset get exported too. This is due to the nature of relationships, where the export assumes you want all the discrete features and tables that inform the relationships. There is no harm in deleting this relationship from the sample data as described in these topics. However, if you are exporting from another production database, you likely do not want to delete this relationship, as it would delete data associated with the relationship too.

    In short, the next step describes deleting the relationship so that electric and conduit features/tables do not get exported along with your fiber features/tables.

  4. Expand the ElectricDataset and locate the relationship ConduitSystem_FiberOpticCable.
  5. Right-click ConduitSystem_FiberOpticCable and choose Delete.

  6. Click Yes to confirm the delete.
  7. With the relationship removed, you are ready to export the schema. To start, right-click the FiberDataset and choose Export > XML Workspace Document.

  8. In the Export XML Workspace Document, choose Schema Only.
  9. In the same dialog, use the Browse icon to specify a location to save the XML file. The location and name of the file are up to you, simply choose a place and name you prefer. Then, click Next.

  10. On the next page of the dialog, confirm the fiber features, tables, and relationships are included in the export.

    IMPORTANT: If at this point you see electric and conduit features, it means you did not delete the ConduitSystem_FiberOpticCable relationship, and the application wants to include the other datasets. You could uncheck the superfluous features, but it is likely faster to Cancel, delete the relationship, and return to this dialog.
  11. After looking through the list of items, click Finish.
    IMPORTANT: This export uses Minerville’s NAD1927 State Plane Colorado North FIPS 0501 coordinate system. You should reset your coordinate system, extent, map units, etc., as needed.
  12. When the export is complete, you are ready to import. To start, right-click your new geodatabase and choose Import > XML Workspace Document.

  13. In the Import XML Workspace Document dialog, choose Schema Only.
  14. In the same dialog, use the Browse icon to locate the exported XML file you created earlier. Then, click Next.
  15. On the next page of the dialog, read through the features, tables, domains, and relationships about to be imported. Then, click Finish.
  16. Once complete, expand your new geodatabase and view the features, tables, and relationships that now exist.

At this point, you have the basic schema imported. However, you do not yet have the ArcFM properties set, which include model names and autoupdaters. Continue to the next topic to export and import those properties.
QR code for this page

Was this helpful?