The process for moving customizations from one project to another is:
-
Compare the delivered schema configurations with the customized schema configurations and generate instructions for the differences.
-
Use these instructions to update the non-customized project with the customizations.
An alternative procedure that will work if the project to be customized is based on the same schema delivery and hasn’t yet been customized is:
-
Compare the non-customized project schema with the customized project schema and generate instructions for the differences.
-
Use the differences to update the non-customized project schema.
If the non-customized project is based on the same schema delivery and this project has no customizations, then the CMF file from the customized project can simply be copied and replace the CMF file from the non-customized project.
Comparing Delivered and Customized Schema Configurations
To compare the delivered and customized schema configurations, the delivered schema file must be available. If this file no longer exists on a customer’s machine, then the EFHistory.cmf file being delivered with the SmartPlant Foundation upgrade software can be used to come up with the delivered schema for the corresponding schema configuration.
The comparison of the delivered and customized schema configurations should be done by opening the delivered schema file and setting the appropriate active configuration. A comparison should then be made with the corresponding configuration in the customized schema file and the instructions generated for the differences between the two configurations.
To update the non-customized schema, the non-customized schema file should be opened and the active configuration set. The previously generated instructions should then be loaded into this configuration.
Direct Comparison of Non-Customized and Customized Schema Files
If the non-customized schema file can simply be replaced by the customized schema file, then copying the customized CMF file and replacing the non-customized CMF file with this file is the simplest solution.
If either there has been some unique customizations done to the “non-customized” schema file or if some but not all of the customizations done to the “customized” schema file are to be retrofitted into the “non-customized” schema, then the process should be to compare the non-customized schema file with the customized schema file and selectively update the non-customized schema file with the desired subset of differences between the two files.
This type of comparison is done by opening the non-customized schema file, setting the appropriate active configuration and doing a comparison with the corresponding configuration in the customized schema file with the command to Selectively Update based on the comparison. The desired subset of differences to reconcile can then be user selected.