Problem with versioning

iwkash

Hello All,

Ideally in teamsite, we would have the first version for any DCR as 0 and then the successive ones as 0+, 1, 1+ and so on.

However, we have migrated data and generated DCR through perl scripts. The first version now itself is 0+. If anyone makes some unwanted changes and and then clicks on UNDO CHANGES, the DCR gets deleted. We have a huge list of DCR's and it is not feasible to deploy every DCR and make it version 1 or so and then continue.

What i need is - Is there any method by which i can convert the version of all these DCR's to a baselined (deployed state) version , 0 (or 1) , so that if someone makes changes (making it 0+ (or 1+)) and does UNDO CHANGES, he is taken back to version 0(or 1) ??

Thanks!!

jagadesh

Hello All, Ideally in teamsite, we would have the first version for any DCR as 0 and then the successive ones as 0+, 1, 1+ and so on. However, we have migrated data and generated DCR through perl scripts. The first version now itself is 0+. If anyone makes some unwanted changes and and then clicks on UNDO CHANGES, the DCR gets deleted. We have a huge list of DCR's and it is not feasible to deploy every DCR and make it version 1 or so and then continue. What i need is - Is there any method by which i can convert the version of all these DCR's to a baselined (deployed state) version , 0 (or 1) , so that if someone makes changes (making it 0+ (or 1+)) and does UNDO CHANGES, he is taken back to version 0(or 1) ?? Thanks!!

You should understand the concepts of Staging, Workarea and versioning
When you create new file in workarea should be 0+
When you submit the file to staging it called 1
Again you change the file in workarea it has moved to 1+

My suggestion should be here submit the files to staging, it will be available with vesrion called as 1. Unless the submission to staging from workarea the baseline files wont be availabe .