I recently came across an error in an assembly where the dialogue is "Member row deleted from factory". The assembly is created by another user. When I insert as a sub-assembly into a new assembly the error does not show up right away; only after saving or updating the new assembly. Typically, I will just open the sub-assembly causing the error, check out the file from the vault, open the factory table and direct it to the correct reference. Then I would save and check in.
Here is the issue. The part is missing from the table, but I cannot just add a new row member since there are suppressed features. I could replace it with the wrong part (with wrong features for the sub-assembly). When the other user opens the sub-assembly there is no error. He believes there is a local copy of that instance on his hard drive. It is not in the vault, so it errors when the part is retrieved for other users.
1. What is a safe way to correct this conflicted reference without creating more problems between the vault and local copies?
2. How can the user with the local reference merge it back into the sub-assembly in the vault?
|