Using PDMLink 9.1. I had a user change the names of some the instances in a family table and check them in. The result as you can imagine is that the old instances are stuck with the previous iteration of the generic and the assemblies in his workspace are complaining. Looking for the steps to reverse this. I will try to replicate on my test server but if anyone has documented this, please send. I know it involves some sleight of hand with PDMLink which I've done before at great pains. Here is what I do know:
* Two different generic instances cannot coexist in same workspace.
* Cannot check out previous instances due to above.
* Cannot delete latest iteration of generic since it means deleting new instances, cannot due in same delete action.
Ugh, what a mess.
Antonio Villanueva - Sr. Software Engineer - ISR Systems
CONFIDENTIALITY WARNING: This message may contain proprietary and/or privileged information of UTC Aerospace Systems and its affiliated companies. If you are not the intended recipient please 1) do not disclose, copy, distribute or use this message or its contents, 2) advise the sender by return e-mail, and 3) delete all copies (including all attachments) from your computer. Your cooperation is greatly appreciated.
1. Check out latest generic and all current instances.
2. Go to PDMLink and find the instances you want to add back in.
3. Check out to the workspace. It will fail with an overwritable conflict. The resolution will merge the instance back into the table and add the item to the workspace.
4. Repeat for other instances.
5. Validate table is correct and check in.
This puts us back to a state where nothing will fail but now we have two copies (instances) in the system. I would recommend a purge to clear the entire history at this point. From here, you can fix the rename issue that cause it in the first place or follow these steps to properly remove the unneeded instances.
