You have now successfully exported data to the target system after following the procedures documented in the previous section. Similarly, you can also export documents to the target system using the sample DESIGN_DOC.csv file and the other supporting files located on Smart Community. For more information, see Find sample data on Smart Community.
This section walks you through how to import documents, validate them with auto-generated rules, and run a job in Data Validator. However, since you are already familiar with tag mapping, this section will not have detailed procedures. It is intended as a guide to enable you to map documents.
-
In SmartPlant Foundation, each document consists of three parts, a master, a revision, and a version.
-
The delivered Data Validator staging system adapter for SmartPlant Foundation server allows the export of documents to the Data Validator target system using the export mapping for document revisions and masters.
-
The import mapping does not have versions, so a version is automatically created for each revision when exported.
-
To map version object properties in the target system, you must map the properties to the revision class definition in the staging system. These properties are instantiated only on the version object in the target system.
Follow the procedures outlined in Getting Started to create the import definition, column headers, and job definition.
-
Create an import definition using the sample input file, DESIGN_DOC.csv, located on Smart Community. For more information, see Find sample data on Smart Community. Follow the same procedure outlined in Create an import definition. You can name the import definition ImportDef-Documents with a description Import definition to load design documents. Select the Auto-Generate Export Mapping and Auto-Generate Validation Rules options in the Create New Import Definition dialog box.
-
You must map the column headers available in the Column Headers pane to an object, property, or relationship in the target system. You must create a column mapping for each of the column headers available under the ImportDef-Documents import definition. This is required to load the data available in the sample input file to the target system. Use the sample mappings provided in the following tables to create your mappings.
-
If an object, property, or relationship in the target system already exists in the staging area, then you must rename the object, property, or relationship while saving the respective mapping. For example, when mapping the Name column header to the SPFDesignDocMaster classification, you must modify the class definition name by adding a prefix, for example SDV, and type SDVSPFDesignDocMaster in the Maps to Object box.
-
The Relationship Mapping option is not enabled until at least two objects have been mapped.
-
You can use the SmartPlant Foundation SmartConverter for hotspotting drawings. For more information, see Configuring the SmartConverter for Graphical Navigation.
You can use the following illustration and tables to create your own document mapping using the sample DESIGN_DOC.csv file and other attached drawing files in the Documents folder available on Smart Community. For more information, see Find sample data on Smart Community.
The objects and relationships highlighted in red are mandatory for document mapping.