Object mapping by class definition - SmartPlant Foundation - IM Update 48 - Help - Hexagon

SmartPlant Foundation Help

Language
English
Product
SmartPlant Foundation
Search by Category
Help
SmartPlant Foundation / SDx Version
10
SmartPlant Markup Plus Version
10.0 (2019)
Smart Review Version
2020 (15.0)

A column header can only have a single object mapping, but can have multiple mappings of different types. The following is an example of creating the object mapping Maps to Object PPMTag with action Create Update.

  1. In the Mappings pane, select the Object Mapping option in Add New Mapping.

  2. Select the Local tab at the bottom of the Mappings pane.

  3. Type *Tag* in the box and click Search to search for all the objects in the local staging area that have Tag in the name.

  4. Select the PPMTag object from the results in the list box, and click Add . The Maps to Object PPMTag with action Create Update mapping is added to the column header.

  5. In the Maps to Object box, type an object name or select an existing object name to map to.

    Do not start the object name with the letters, MSR or HEX, as these are reserved for the delivered mappings and may cause issues due to uniqueness constraints.

  6. If necessary, change the Object Action to another selection. For a list of object actions, see Actions.

  7. To add unique identifiers (UIDS) that match the existing object, such as Tag, Plant Code, or Tag Name, click Create Unique Identifier .

    • The unique identifiers (UIDs) must be set on all objects that Data Validator exports from the staging area. You must set the correct UID in the import mapping by setting up the UID definitions for any object mapping.

    • The Unique Key definition and Unique ID Definition boxes are populated with values that are configured for the class definition currently being mapped to. Once they are propagated, they are not updated again and must be updated manually by loading the class XML file with the new Unique ID Definition and Unique Key Definition.

  8. To add optional interfaces for the selected class definition, click Optional Interfaces . This option is available for object mapping with Create Update and Update actions.

    • The Select Optional Interfaces option allows you to select optional interfaces that are available for the selected class definition in the target system. The selected optional interfaces are instantiated on the objects during export.

    • If you do object mapping with the document revision class definition, the Select Optional Interfaces dialog box displays the optional interfaces for both the revision and version. If the selected optional interface is available for both the revision and version class definitions, during export the optional interface gets instantiated for both the revision and version objects.

  9. Add a prefix for the object type if required, for example TG.

    Do not use MSR or HEX as a prefix as these are reserved for the delivered mappings and may cause issues due to uniqueness constraints.

  10. Select the Mandatory Object option to indicate that the column is required to have a value.

  11. Click Save.

  • When any cell used to create the unique identifier is blank, an error is included in the validation report indicating which cell or cells are missing values.

  • If an object in the target system already exists in the staging area then Data Validator will ask you to rename the object when saving.

  • If the Mandatory Object option is selected and the column has no value, an error is included in the validation report.

  • If you select both the Ignore properties for blank values and the Is Mandatory options during object mapping, if a property has a value in the CSV file, which is a default value specified in the Text values that represent blank option in the System Options wizard, the property will be skipped during import. Validation errors will not occur during the validation stage.