Create a New Pseudo File in the Schema Editor - Integration - Update 44 - Help - Hexagon

The following steps explain how to create a pseudo file in Schema Editor. Pseudo files allow for the objects within the configurations to be logically organized into files. Creating a pseudo file can be helpful to use when making changes to the SmartPlant Foundation schema or creating customizations.

Create the Pseudo File

1. After you check out the schema CMF file from the Desktop Client and launch the Schema Editor, click Tools > Schema > Advanced > Create Configuration.

2. On the Edit Configuration dialog box, type a name and description.

   The name must end in .xml in order to create the configuration as a physical file.

   

3. Select the option Configuration is a pseudo file to create a pseudo file.

4. Click OK.

   

   • You do not need to select an option for Starting configuration when creating a pseudo file. Selecting the option Starting configuration creates the configuration as a primary configuration rather than a pseudo file.

   • You do not need to enter values in the Path to pseudo file box. Leaving the Path to pseudo file box blank creates the pseudo file in the same folder as the CMF file.

   • The ContainerID for the file is set automatically.

Set up the Correct Configurations for New Objects

1. In the Schema Editor, click Tools > Schema > Set Active Configuration to open the Set Active Configurations dialog box.

2. Select the options to set up the correct configurations for new objects.

3. Select the new pseudo file from the Pseudo file for new objects list.

4. Click OK.

5. Click File > Save > Schema File to save schema files, including the new pseudo file.

6. Exit the Schema Editor.

Set the Container ID for the New Pseudo File

1. Open the pseudo file in a text editor.

2. Edit the pseudo file to manually set the ContainerID to a value that represents the use of the schema.

   

3. Save the changes.

   

   • The default ContainerID for a pseudo file is a numeric value automatically set when it was created.

   • The ContainerID identifies schema previously loaded into the SmartPlant Foundation database when performing the compare during a load.

   • The ContainerID in the header updates to match that in the pseudo file the next time the CMF file is opened.

   • After setting the ContainerID for the pseudo file, the new schema can be modeled in the Schema Editor, or it can be cut and pasted into the physical pseudo file.