Pseudo files and ContainerID - 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)

To load the schema into the SmartPlant Foundation database, it is necessary to first extract a single version schema from the multi-version CMF file. The main CMF file is extracted into a file called SCHEMA_EFSchema-Gen.xml, which has a ContainerID of Core.EFSchema. When loading this file into SmartPlant Foundation, there is an option to compare by ContainerID to perform deletes on schema items that have been removed.

When creating a separate physical pseudo file the user has to enter a unique ContainerID for that file. This can then be used for comparison on load to manage changes to schema modeled in that pseudo file. The ContainerID is composed of two parts, foldername.filename, so that when the Export By Container command is used in SmartPlant Foundation, the schema is exported to the identified subfolder and file name. An example ContainerID might be ProjectXYX.WorkPackageSchema.

If you move schema between the pseudo files or the CMF file, then you change its ContainerID, this results in the deletion of schema from your SmartPlant Foundation database if you also first load the file from which the schema was removed and use the Compare By ContainerID option. When moving schema between files, we recommend that you first load the files without the Compare by ContainerID option so that the schema is not deleted. This updates the ContainerID on the relevant schema in SmartPlant Foundation, making Compare by ContainerID possible on subsequent loads.