| Applies To | |
| Product(s): | OpenPlant CONNECT Edition Update 9.1 |
| Version(s): |
10.09.01.08 |
| Environment: | Windows 10 (64-bit) |
| Area: | Maintenance Key-in |
| Subarea: | PlantSight Integrated WorkSet |
| Original Author: | Deepak Singh, Bentley Product advantage Group |
In this wiki article, we will explore the maintenance key-ins which are handy to fix the sync issues. Please refer to the scenarios below and apply the appropriate key-in as required. Please familiarize yourself with the Warning details mentioned for each key-in prior to executing them.
Scenario: Upon sync operation application prompts that issue related to reserved components tags.
Warning: If a component tag was reserved for a legitimate reason it will also be released. The limitation is that it will only release component tags that are reserved by the current User. To release tags reserved by other users, the Engineering Data Manager portal should be used.
Scenario: Upon sync operation application prompts the issue related to the reserved drawing instance tag.
Warning: If a tag was reserved for a legitimate reason it will also be released. A limitation is that it will only release Document tags that are reserved by the current User. To release tags reserved by other users, the Engineering Data Manager portal should be used.
Steps to Accomplish
Scenario: Opening a copied PID document in a specific workset prompts the File Modification dialog. If mistakenly, the option of "The file was moved or renamed" is selected then we will end up with duplicate GUIDS for the document and components which lead to sync issues.
Warning: If we execute this key-in, all DGN files in the same folder as the open file will have their GUIDs regenerated which could break the relationship to what has already been synced to PlantSight for documents that did not require new GUIDs.
Scenario: If the application crashes during sync and we get an error that the local BIM briefcase has corrupted. In this situation, we can use key-in to obtain a new one.
Warning: Any existing tag reservations that had made will be lost.
Scenario: If we wish to reuse a Dgn that was synced to a previous iTwin in a new iTwin, then we should use key-in PID PlantProject reuse. If, however, that was not done before reusing the old DGN in a new project, we need to Reset the "Is Reserved" flag for the document and all the components instances.
Warning: To be used only in the described scenario. This means if the IsReserved Flag is true for a document and its components that are not previously synced to the current iTwin. If we use mentioned key-in on a Dgn which is synced to the iTwin that Dgn will no longer be useable as the State of the Tag Reservation in the iTwin hub and the DGN will get out of sync. We have to delete the document and all the components from Engineering Data Manager then we can perform re-sync the data from this Dgn
If the above problem persists, then please create a Service Request and contact the Bentley Product Advantage group. Please include a list of all relevant details to get an in-depth analysis for a solution or workaround.