Regardless of whether you want to extend the SmartPlant Foundation schema to create custom class definitions and relationships or a simple custom property, the following work process describes how you open the stand-alone schema files in the SmartPlant Foundation Schema Editor, save your changes to an extension file, and load the changes into the SmartPlant Foundation database.
As you make changes to the schema, you should store your modifications in a schema extensions file, which is added to a configuration file. The extension file is dependent on the original SmartPlant schema, which is set to read-only in the configuration file. For more information, see Create a schema extension file and Modify a File Configuration.
When you make modifications to the schema using an extension file, any modifications that you make to the schema are saved in that extension file, not the delivered SmartPlant schema files. When you create new relationship definitions in your extension file, at least one object at one end of the relationship definition must exist in your extension file. For example, you cannot create a new relationship between two objects in the SmartPlant schema. However, you can create relationships between objects in your schema extension file and the SmartPlant schema.
For more information about using configuration files to manage schema changes, see File Configurations.
The delivered model files are available on Smart Community. For more information, see Find sample data on Smart Community.
The model definition files (.xmlsrc) control which sets of model files are to be built into a database using an administrator role.
For example:
Authoring.xmlsrc lists the following layers
-
SchemaComponent
-
Bootstrap
-
Core
-
Common
-
Auth
-
AuthExample
-
AuthPlantData
What do you want to do?