Deleted Items
- Last UpdatedApr 24, 2023
- 1 minute read
Deleted items in the model are recorded as deleted during the Compare phase and remain in the reference model to be deleted later if not required. This separation of operations is so that you can see what will be deleted during the Merge process. Before deletion the objects are changed in colour so that they may be identified.
Note:
An item is not actually deleted from the original model. The apparent deletion may,
in fact, be because the item was never transferred to AVEVA Bocad Steel in the first
place due to some reason. Alternatively it may have been created in the base product
since the initial Export process had taken place.
'Deleted' items are disconnected from the old model and transferred from the current part of the database into a STRU created under the special 'Deleted' SITE.
As with the added items, the STRU is named out of components, thereby enabling you to determine at which version items may have been removed from the model.
For example, a new STRU may be created with the name of /FAB-OLD-DEMO-SYSTEM/A.1 under the special SITE /FAB-OLD-DEMO-SYSTEM. The components of this name are as follows:
|
/FAB- |
the system prefix |
|
OLD- |
identification of new element container |
|
<mdb name>- |
the current MDB, for example: /DEMO |
|
<user name>-/ |
the current user name, for example: SYSTEM |
|
<transfer nr>. |
the current Transfer letter, for example: 'A' |
|
<revision nr> |
the current revision number, for example: '1' |
You would thus be able to find all the 'deleted' items to this MDB at this version.