Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
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.
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 [[image]]
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....
I know this is an OLD post but this would be super useful to have as I have new users that are running into this issue still and need to set the REV level to be the previous level. We are very close to pulling out the entire Vault revision table and tracking it manually as this issue is not being fixed or documented in a way that is easy to find the solution.
To copy from @Anonymous post above this is a great way to explain the issue.
