System ID
The System ID, or SysID, is a unique identifier generated by Creo Elements/Direct Modeling for each item you create. A SysID conflict occurs when Creo Elements/Direct Model Manager finds another model in the database with the same internal Creo Elements/Direct Modeling ID, even if it has a different model name. Creo Elements/Direct Modeling treats models with the same internal SysID as shares.
Creo Elements/Direct Manager Server generates a separate, unique identifier, known as the ELID, which is used only by Creo Elements/Direct Manager Server and its client applications such as Creo Elements/Direct Model Manager. The SysID and ELID are saved in the database to identify models and drawings.
Creo Elements/Direct Model Manager checks for SysID conflicts as part of the Save and Refresh processes. If there is a SysID conflict detected during the periodic refresh between Creo Elements/Direct Model Manager and Creo Elements/Direct Modeling, a toaster notification pops up in the bottom right corner of your screen and SysID Conflict displays next to the model name.
• If a matching SysID is found, Creo Elements/Direct Model Manager will offer you the option to create a new version or overwrite the item that matches the SysID for the item you are trying to save.
• If a matching SysID is not found, a new entry is created in the database.
Important Considerations
It is important to make sure unique parts have distinct System IDs and ELIDs. The following guidelines can help you avoid problems that can be difficult to correct.
1. If you want to save an existing model in the database as a new and unique item, rename the model and use Assign new SysID to local model to give it a unique System ID.
2. If you modify a model or assembly and you do not want that change reflected in all instances of that item, make a copy first and save the item as a new entry in the database.
System ID Conflicts
You will get a SysID conflict if you try to save an item with the same System ID as an item already in the database. Most SysID conflicts occur when importing data that already exists in the database.
For example, different designers might start with the same model, but modify the geometry into completely different parts, such as a casing or a mold. If the new parts were saved to package files without making a copy of the original part first, the new parts have the same System ID as the original parts. In this case, the new parts should not overwrite the existing part.
In another example, a designer might import a part that contains subassemblies already imported into the database by another designer. In this case, the designer will need to verify that the subassemblies really are the same.
When Creo Elements/Direct Model Manager detects a SysID conflict during a save operation it displays the Conflicting models found in the database dialog.
• If you know that you want to save the local model, click Continue to Save. The Save dialog will appear so you can overwrite the database model with the local model, or save the local model as a major or minor revision of the database model. Items with conflicts will be highlighted. Use the filter to see only the items with conflicts.
• If you don't already know how you want to handle the conflict(s), click Investigate Conflicts. The Check and Resolve dialog will display the conflicting items. Dock the dialog if you need to investigate several conflicts. Right-click an item in the dialog to use the investigation tools:
◦ Compare local and DB models side-by-side to see both the local and database versions of the item in Creo Elements/Direct Modeling viewports.
◦ View properties of DB model to see information about the database version of the model.
◦ Highlight local model to see which specific part of the local model has a conflict.
◦ Assign new SysID local model to save the local model as a new model.
From the right-click menu you can also,
◦ Replace local with DB model to replace the local version of the conflicting part with the version from the database.
◦ Replace DB model with local model (DB Overwrite or New Version) to replace the version of the model in the database with the local version.
 |
You must reload the model after a save that produced SysID conflicts to maintain the integrity of the Masterdata.
|