Is there a method to disable the synching of a class of components such that the sync mapping does not default to that of a higher class? For example, the INSTRUMENT class is mapped and synched to the plant project database. The INSTRUMENT_DISCRETE_ANALOG class is a subclass of INSTRUMENT and currently has it's own mapping and is synched to the database. I want to disable the synching of INSTRUMENT_DISCRETE_ANALOG components to that they are not placed in the database at all. If the mapping of the INSTRUMENT_DISCRETE_ANALOG is removed, they will be mapped and synched to the database based on the definition of the INSTRUMENT mappings because INSTRUMENT is the parent class. I attempted to deactivate the mapping of the INSTRUMENT_DISCRETE_ANALOG class by removing the checkmark next Active in Class Editor. This resulted in unexpected and wildly inconsistent behavior: * Newly create objects were still synched into the database. * Subsequent synchs attempted to create new database records for these existing objects, which resulted in errors associated with duplicate primary keys. * The database records will not be deleted if the component is deleted from the P&ID, resulting in orphaned database records. The errors and inconsistencies caused by the inactive mapping are a separate issue. Can anyone identify a method to disable the mapping of a class of objects so that they are not synched between a P&ID and the plant project database even though a parent class is synched? Thanks.
↧