With the schema in place, you are now ready to import the ArcFM properties. This step assigns the model names and autoupdaters
that are required for Fiber Manager functionality.
- In your new geodatabase, click on the PatchLocation feature
class, then click the Autoupdaters tab.
- Notice, no autoupdaters are assigned to any task or field.
- Click the Model Names tab, and again notice no models names
IMPORTANT: This simply demonstrates that while you
have the features and tables, you do not yet have the ArcFM properties.
- Locate the Minerville sample geodatabase.
- Right-click the Minerville sample geodatabase and choose ArcFM XML Export.
- Check the following boxes:
- ArcFM Model Name Information
- ArcFM Properties
- ArcFM Relationship Class Info
- ArcFM Snapping Information
- Domains (scroll down to see this option)
IMPORTANT: The domains are the reason why you are
exporting from the geodatabase level instead of the FiberDataset level.
Certainly, the import schema steps in the previous topic brought along
domains, but only those that were actually assigned to the sample
data features/tables. There are many more fiber domains ready to be
assigned that are included when exported from the geodatabase. Yes,
this means that domains in other industries are included in this export.
Further, the export includes properties and settings for other industries.
Regarding the properties and settings, when you import, it does not
import superfluous settings as those other features/tables do not
exist. In other words, although it is going to export properties for
electric and gas features, those do not get imported because electric
and gas features do not exist in your geodatabase.
- Using the Browse button, choose a destination and name
for the exported XML. Then, click Export.
- When it is finished, click No, you do not need to export
- Locate your new geodatabase.
- Right-click your new geodatabase and choose ArcFM XML Import.
- In the ArcFM XML Import dialog, choose Overwrite.
IMPORTANT: Overwrite is acceptable in these steps
because you are starting with an empty geodatabase. If importing against
an existing production database, you would likely choose Keep Existing
(or Prompt if you want to handle duplicates on a case by case basis).
- Click the Browse button to locate the exported XML you
- Optional: As required by your geodatabase implementation,
to pre-pend the schema name or database and username, modify one of
the .xsl files included in the ArcFM installation at "C:\Program Files
(x86)\Miner and Miner\ArcFM Solution\Bin\Style Sheets." Modify either
"prefix_Oracle.xsl" for importing into Oracle, or "prefix_SQLServer.xsl"
for importing into SQL Server.
- Click Import.
- When finished, you might see a message that some information
could not be imported, and you can view this information. It is all
the properties for other utility features that do not exist. In other
words, the export included properties for electric features, but because
electric features do not exist in your geodatabase, they could not
- After viewing (or not viewing) the unsuccessful imports,
click No to attempt another import.
- In your new geodatabase, click back on the PatchLocation
feature class, then click the Autoupdaters tab.
- Notice, autoupdaters are now assigned. Remember, these
used to all be null.
- Click on the Model Names tab, and notice model names are
This holds true for all features, tables, and relationships,
and it demonstrates the time-saving benefit of exporting and importing.
You now have a configured geodatabase with the standard data model.