AnsweredAssumed Answered

PDM Workgroup - Force an "Older" revision

Question asked by Daen Hendrickson on Apr 11, 2011
Latest reply on May 5, 2016 by Daen Hendrickson

We are using SW2011 SP3

 

We modified our revisioning scheme recently. We changed from a single Alpha (A-Z) with no lifecycle enabled to a something more along the lines of ANSI:

 

In Development (-, 01 through 99)

Released (A-Z except I, O, Q, S, X)

Obsolete (same as released)

 

We have some files that were checked into the vault under the old scheme and have a revision of B. We are ready to check them in again and are trying to "convert" to our new revisioning scheme but PDM won't allow it. Although the lifecycle status is set to "In Development" both in the part file and in the vault, when we try to manually change the revision to 03 (instead of C) PDM tells us the revision it too old.

 

I tried turning off lifecycle in the vault but still no change.

 

The odd part is I did exactly what I propose a few weeks ago. I had files created under the old scheme, changed them to numeric and checked them in under the new scheme. However, we still had SW2010 SP4 installed at the time. And now I am not sure exactly what steps I took to get it to work. However, I am pretty sure there were no unusual tricks to get it to work.

 

Both the guy having trouble and I are administrators in PDM.

 

Any suggestions on how to get these files checked in as "In Development" and revision "03" from a current status of "In Development" and revision "B"?

 

Thanks, Daen

Outcomes