The following section describes the rules and behavior for the Smart 3D metadata adapter.
Metadata Save Behavior
Metadata is saved when the tool schema is saved.
Rules for Application Classes
For this release, Smart 3D does not support adding new classes to tool metadata using the metadata adapter. Adding new SPMapClassDefs for Classes only creates a map object in the tool map schema. However, you can create new interfaces (IsInterface = True) for an existing class using the metadata adapter.
Rules for Application Properties
Smart 3D does not support adding properties to system-defined interfaces (also referred to as packages). However, users can add new properties on existing interfaces in the user-defined package.
Rules for Application Enumerations
-
Adding new enumerated lists (code lists) is supported in the tool.
-
Publish mapping is not required for enumerated lists (code lists) because the Smart 3D adapter maps automatically based on the enumerated list entry number. However, the number must match in the SmartPlant schema, the Smart 3D tool map schema, and the tool metadata.
Rules for Application UoMs
Changes to SPMapUoMListDefs will only be made in the tool map schema (SP3DPublishMap.xml). The tool database will not be updated with these changes.
Rules for Application Relationships
Adding and deleting SPMapRelDefs is supported in the tool. However, adding and deleting SPMapRelDefs to certain objects defined in the system package are not allowed in the tool.
Rules for Application Edges
Any changes to SPMapEdgeDefs will only be made in the tool map schema (SP3DPublishMap.xml). Tool database will not be updated with these changes.