Revision change

[Anonymous]

Hi,

 I just uploaded an assembly converted from another CAD system.  I am manually assigning Revisions to files ( hopefully a one-time-deal).

  As it happens, I assigned an incorrect revision number to a file ( C instead of B).   

The files has category ' engineering' and is in ' work in progress'.  It does not let me correct the  revision number  back to a 'B'.

  Does anybody know how to correct this typo ? (except for deleting the file from the vault or some other  awkward way of fixing this  🙂  ).

 Thanks

[Anonymous]

Hello @Anonymous,

I believe Vault is behaving as designed.  The revision engine is only meant to move "forward".  I tried changing revision schemes, changing categories, mapping to a UDP, all with the same results; "Next revision 'B' is unavailable".  Looks like you'll have to delete and check in again.

[Jason.Courtemanche]

Hi @Anonymous,

Welcome to the Autodesk Community, and thank you for posting your question here in the Vault forum!

@Anonymous is correct if you change the revision to a higher number you cannot change it back. One of Vaults features is to track data. I find if you use the categories to auto assign files to lifecycles. Then move the files through the lifecycle states and let it automatically update the rev sequentially. 

If you are adding files to Vault from another system and trying to manually update the rev to match the state of the other system can be difficult. Since if you chose the wrong setting you have to start over. If you need to bring over a lot of data and preserver the current file history, I would recommend working with a reseller to help move the data. 

Regards,

Jason 

[Anonymous · Accepted solution]

Thank you @Anonymous and Jason,

 yes,  the vault is intended to move revisions forward.  I was hoping I would still have control over the revisions ( both direction), since the is still in the 'work in progress state'.  That is not the case.  

Thank you for your help.   tomr4226

[Anonymous · Accepted solution]

Depending on how far down the rabbit hole you want to go, there exists a work around, although very awkward.  So the following is more an academic exercise than actual workable solution.

Because of the sequential nature of the revision engine, you can create a revision scheme that has B coming after C.  

1. Create a copy of the revision scheme that is assigned to the file.

2. Create a copy of the revision scheme format

3. Move B down after C

4. Assign this copy of the revision scheme format to the copy of the revision scheme as the primary scheme format

5. Start the Change Revision command on the file

6. Change the revision definition to your recently created one

7. Set revision to the next available (should be B, if it is currently C)

This leaves the file stranded with the "awkward" rev scheme.  Since you can't only change a revision scheme without actually changing the rev level itself, we are limited options on what to do next.  The revision engine senses we are on the third rev (A, C, B) and when we try to do a rev bump using the original rev scheme, it will want to use the fourth rev, which would be D (if we are using the Standard Alphabetic Format; A,B,C,D).  And we cannot have duplicate values in a given rev scheme format (no A,C,B,C), we essentially lose the C rev, unless using the secondary rev is acceptable, again in the case of the Standard Alphabetic Format, it would be B -> C.1.

 

[maxim.teleguz]

it is convoluted. because PDM is all about having a history of files. If we delete something just to keep the sequential order we now lose data. 

what is more important? 

Historical data or a revision character?