Edit the custom mapping template files - Intergraph Smart Interop Publisher - Help

Intergraph Smart Interop Publisher Help

Language
English
Product
Intergraph Smart Interop Publisher
Search by Category
Help
Smart Interop Publisher Version
17

Populate the custom mapping template file related to your format type with the required classes and properties. To help you map classes and properties to existing ones provided by Smart Interop Publisher, you can refer to the delivered SPIOPSchema.xlsx file to help you get the correct names.

Notes and Recommendations for Custom Mapping

  • Custom mapping for Smart 3D does require you to specify the source interfaces. Other format types currently supported do not have that requirement.

  • You can use custom mapping to completely remap classes and overwrite the target classes.

  • If you add new classes, interfaces, and properties that are not available in the SPIOPSchema.xlsx file, you must also make sure these new entries are inserted into the Smart Interop Publisher schema (SPIOPToolMap.xml), and the schema for your target application (Smart 3D and SmartPlant Foundation). For Smart 3D, you must also edit the delivered CustomR3DSchema.xls file to add your new schema. For SmartPlant Foundation, use the Schema Editor to add the new schema.

  • Any new custom interface names must contain the “R3D” substring. Otherwise, the software does not map the properties contained in the interface.

  • The exclamation point (!) in the A column comments out or excludes that row.

  • Check the use of a colon (:) in the property names as you add them into a custom mapping file:

    • For MCAD and PDMS formats, a colon placed in front of the property name is replaced with a hyphen (-) during translation. For example, if you enter :Status for the property name in your custom mapping file, the resulting translation shows the property name as -Status. Instead of a colon, enter the hyphen in the property name for these formats.

    • For all other supported formats, a colon placed inside a property name is removed during translation and replaced with a space. For example, if you enter Net:Area for the property name, the resulting translation displays Net Area.

  • To review the template file, see Mapping Template File Contents.

This section contains the following workflows to edit custom mapping: