Property and relationship mapping - SmartPlant Foundation - IM Update 48 - Help - Hexagon

Properties on the Data Capture document master, revision, and version can be mapped to any of the properties on the FDW document master, revision, and version. This can be done by using the XLST_Data_Data CaptureFDWPropertyMappings.xlsm file found in sample data located on Smart Community. For more information, see Find sample data on Smart Community.

1. Add property mappings in the Data CaptureFDWPropertyMapping sheet.

2. Navigate to the Read Me sheet, and click Create All Load Files to generate an XML file.

3. Load the generated XML file into the SmartPlant Foundation Desktop Client using the Loader to generate property mapping objects. For example, by default the SPFNClientDocTitle property of the SPFNDocumentVersion class definition in Data Capture is mapped to the SPFTitle property of FDWDocumentMaster class definition in FDW.

Relationships can also be copied to the FDW document from the Data Capture document using relationship mapping. Data Capture document master, revision and version relationships must be configured to FDW document master, revision and version respectively.

Relationship mapping is configured like property mapping, but is done using the XLST_Data_Data CaptureFDWRelationshipMapping.xlsm file, delivered in the same location as the file used for property mapping.

1. Copy the existing relationships from the Data Capture document to the FDW document using the XLST_Data_Data CaptureFDWRelationshipMapping.xlsm file found in sample data located on Smart Community. For more information, see Find sample data on Smart Community.

2. In the .xlsm file, provide the values for the columns as listed below:

   • Data CaptureClassdef - must be one of the document part class definitions of the Data Capture object (SPFNDocumentMaster, SPFNDocumentRevision, or SPFNDocumentVersion).

   • Data CaptureReldef - must be a Data Capture relationship definition UID that the FDW relationship definition should be mapped with.

   • IsData CaptureRelDefDirection12 - must be set to TRUE if the interface of the specific document part (master, revision, or version) is on End1 of the relationship definition are you copying. False indicates that the document object is at End2 of the relationship.

   • FDWRelDef - must be a FDW relationship definition uid with which the Data CaptureRelDef column value should be mapped with.

   • FDWClassDef - must be a FDW class definition that realizes the interface at the other end of the FDWRel from the document part. It cannot be a document part.

   • IsFDWRelDefDirection12 - must be set to TRUE if the interface of the specific document part (master, revision, or version) is on End1 of the relationship definition. False indicates that the document object is at End2 of the relationship.

   • CreateFDWObject - must be set to TRUE if the object other than the document part object should be created.

For example, SPFNFDWDocDiscipline is mapped to SDADocDiscipline by default by specifying the following:

Property mappings can be created between different document parts, but for relationship mapping, the Data Capture and FDW document parts specified in the mapping must be the same level: master, revision, or version.