Find the ENOVIA Object ID from DesignSync

When a business object is connected to a file or folder in a DesignSync server, the metadata about the business object and the connection is stored in DesignSync.

The metadata information consists of the business object ID in the 3DSpace Service and the selector identifying the file or the folder version that is connected to the business object.

The syntax for printing the value of the business object ID stored in DesignSync is as follows:

Print bus TNR select | vcfile.businessobject   |
                     | vcfolder.businessobject |

The business object ID is stored even when an empty connection is created. When a file or a folder is eventually checked in against this empty connection, DesignSync associates the saved business object ID with the version of the checked in file or configuration of the checked in folder.

Any command that results in the creation, deletion, or modification of connections between business objects and files or folders on a DesignSync server causes the metadata to be updated in the 3DSpace Service as well as in DesignSync. The command completes successfully only if the operations involved are successful at both ends.

The metadata in DesignSync is affected and can change when a connection is established between a business object and a file or a folder in DesignSync or an existing connection is deleted or modified. Additionally, the metadata in DesignSync is updated during the following operations in ENOVIA products. In the following cases except where indicated, the system tries to perform the update after the transaction has finished. So any failure of the update does not affect the action performed in the ENOVIA product.

  • When a business object is deleted, any references to it in DesignSync are removed.
  • When a business object in a DesignSync store is cloned, the connections associated with the object are copied to the newly-created business object (if the default copy files option is used) and DesignSync metadata is updated to record information about the new business object.
  • When a business object in a DesignSync store is revised, the connections are copied if the inherit files option is used and DesignSync metadata is updated to record information about the new business object.
  • When a business object and its vcconnections are imported, information from imported connections is used to update DesignSync metadata about associations between DesignSync files or folders with the imported business object.

If the connections made during the import process fail, it causes the transaction to fail as well.

  • When a business object ID is changed as a result of commands to change vault or cluster oids, DesignSync metadata is updated to replace the old ID of the business object with the new ID.

In all of the above operations, if the metadata information about the business object cannot be updated in DesignSync, a warning is issued but the operation itself does not fail.