Overview

Currently, when new properties are added mid-project to a parent class within OpenPlant Modeler schemas and an attempt is made to provision these changes to an iModel the process fails with an error indicating that the schemas could not be provisioned successfully.

This limitation requires manual intervention and impacts the efficiency of schema management and iModel provisioning workflows.

Problem Statement

• Adding a property directly to a parent class in OpenPlant schemas leads to provisioning failure in iModel.

• As a result, users must manually add the same property to each individual subclass, which:

  • Is time consuming

  • Increases risk of inconsistencies or errors

  • Reduces overall productivity, especially for schemas with large class hierarchies

Current Workaround

To successfully provision schemas:

• The newly added property must be explicitly defined in every subclass under the parent class.

• This manual duplication ensures provisioning succeeds but adds significant overhead.

Proposed Enhancement

Enhance the iModel provisioning process when properties are added mid-project to automatically include these inherited properties during schema provisioning without requiring subclass-level duplication.