We are using Synergy 7.1. We have recently begun converting our Microsoft Word and Excel document names to use the latest suffix, .docx and .xlsx. We have not been having any issues with this until we needed to convert the same instance of a document to the new format in two separate Releases. Here is an example:
We created and shipped Prod1-Rel1.0. Once shipped we created a new Release and copied Prod1-Rel1.0 creating Prod1-Rel2.0. In the new project we checked out Doc1.doc-1 creating Doc1.doc-2. We then renamed it to Doc1.docx-2. This works fine and is what we have been doing on a regular basis.
We then had to create a patch so we created a third Release and copied Prod1-Rel1.0 creating Prod1-Rel1_Patch1. We checked out Doc1.doc-1 again, creating a parallel version, Doc1.doc-1.1.1. We then renamed it to Doc1.docx-1.1.1. When we do this, the rename is successful, but the Instance Number of the renamed document changes from 1 to 2.
We have tried several variations on this theme but cannot find a way of performing the rename without the Instance changing. If anyone has a suggestion on a way around this, it would be greatly appreciated.
Thanks for your help,
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
2 replies Latest Post - 2012-07-12T16:17:10Z by AubreyEichel
Pinned topic Renaming Parallel Documents in Different Releases Causes New Instance
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-07-12T16:17:10Z at 2012-07-12T16:17:10Z by AubreyEichel
David.Honey 270001UEBC176 PostsACCEPTED ANSWER
Re: Renaming Parallel Documents in Different Releases Causes New Instance2012-07-12T09:05:38Z in response to AubreyEichelHi Aubrey,
To get the same instance, you would have to check out the first renamed one. You can then replace its contents with a copy of the 2nd release's contents. Optionally, you could modify the successor history links to show its derivation from the 2nd release's contents. Had the file been ascii, a simpler approach would be to do a merge, selecting the renamed file in the first release as the first selection, and the original file in the 2nd release as the second selection.
AubreyEichel 270001XUUW2 PostsACCEPTED ANSWER
Re: Renaming Parallel Documents in Different Releases Causes New Instance2012-07-12T16:17:10Z in response to David.HoneyThank you very much for your suggestions David. I will make them work. Also, thank you very much for your continued support for all of us in this forum. It is greatly appreciated.