Vault Ideas
Share ideas for future product features directly with the Vault team and collaborate on existing suggestions with your peers.

Rollback Revision Increment

Status: Implemented
by Advocate jeff.noel on ‎07-25-2012 12:44 PM



If a user accidently makes a change state of a model from Released to Work In Progress, it will increment the revision, and then leave us with no way to go back to the previous revision.  I understand why you would do this, as we shouldn't be going backwards with Revisions, so I don't believe every user should have access to this functionality, but an Administrator should be able to override the Revision if they determined there was a mistake made and we need to go backwards.



Status: Implemented

This request has been implemented in Autodesk Vault Workgroup and Professional 2016.

By: Collaborator ryan
| Posted ‎03-03-2016 12:56 PM

With your file selected, go to Actions > Rollback Lifecycle State Change

By: Explorer JediDreams
| Posted ‎03-03-2016 01:19 PM

Was actually referring to roll back of revisions. Though I realize this is in the "Lifecyle" category.

By: Collaborator ryan
| Posted ‎03-03-2016 01:22 PM
Well since your revision is likely bumping because of your lifecycle state change (e.g. From Released to WIP, bump revision +1), by rolling back the lifecycle you will get back to your previous revision value.

Ryan Small, Technical Specialist
1.877.438.2231 x110
2300 Steeles Ave West, Suite 240, Vaughan, ON L4K 5X6
By: Community Manager
| Posted ‎03-03-2016 01:44 PM


please take a look on the Vault 2016 help to get more details regarding State/ Revision Rollback capabilty:


Best ergards



By: Explorer JediDreams
| Posted ‎03-03-2016 01:46 PM

In the future that would be the option we would use. However currently we are moving into pro and moving all our existing parts/drawings into lifecyles.


Many of them have revisions already so in the process of moving stuff over accidents happen. While writing our revision back to the vault controlled rev, unintentional changes happen (Human error, only 1 so far, which brought me here), all while still in the design state so there is no previous lifecyle to roll back too.


Through lack of foresight (Or lack of knowledge) we opted to bring everything in at the base state and move it into our custom category/lifecyles at our leisure, so the history often goes....


(Basic example)

version 1 - rev 0 - base/no lifecycle

version 2 - rev 0 - custom cat./design

version 3 - rev 4 - custom cat./design (oops wrong rev)

and that's where I'm stuck :(

Submit Your Ideas

Share and shape product ideas.

Submit an idea
Idea Guidelines

Please review our Idea guidelines and best practices before posting a new idea, or voting on an existing one!