Community
We dont typically release subscription updates for Vault Basic.
So, no it does not apply to the current release of Vault Basic.
Mikel Martin
User Experience Architect
Autodesk, Inc.
While it understandably may appear to our customers that we have released an update that solved a major workflow problem, and this change should be something that can be applied to previous releases. The reality is that the ground work for this change was put in place in the 2014 release. There were several changes put in place within the eco system of server and clients to make this update possible.
It is important to understand this point in order to understand that replicating this change in previous releases of the product is not simple or practical. While we sometimes do update changes to previous releases, this one is not likely to be one of them.
Mikel Martin
User Experience Architect
Autodesk, Inc.
unfortunately, there is no simple "don't do this" and everthing will be better.
The core issue is that some applications give the user the option to write to files even when they are marked as read only. Some applications do this more than others.
When this happens the files in the workspace enter a state where Vault no longer has enough information to help you know what version of the file was modified and what the best course of action should be.
The only way to not get in this state (without the subscription release) is to not save the files when prompted by the appication.
In the subscription update we are gathering and storing enough information to be able to know what the file was before it was modified in order to give the user better information and workflows. We did not stop the files from being modified. Not only is that out the Vault's control, it is not practicle for some applications to make this type change.
Mikel Martin
User Experience Architect
Autodesk, Inc.
Hello,
I am using Vault Basic 2016 through the Inventor 2016 interface and am still getting this error/behavior a lot.
We have recently migrated from a single user environment to Vault Basic.
I've applied the latest service packs on the client computers and the ADMS, and still getting this behavior.
Many times there is not a "no to all" option as in the attached image, and I have to click "no" on every part file individually.
I have done absolutely nothing to modify the parts it's trying to save except for open them read-only in the context of the assembly.
I noticed that when we were setup on single user config that you could save an Inventor assy, then it would tell you it had been modified if you tried to close it immediately afterward. I'm guessing that this issue is somehow at the root of this but I'm not sure what I can do as a better workflow.
I'm hoping we have some setting incorrectly configured because I cannot think that the software is actually designed to work like this...?
Please advise/update.
Ben
IV 2016, Vault Basic 2016 Windows 7
Write enabled – not checked out from Vault. Again, again and again after all those years. I’m on 2022 and I’m really pissed. How many years we have to wait until Autodesk solves this issue. Another decade? We have constant problems with unwanted overwriting of our files. Vault can’t do basic thing that it is intended for. There is absolutely no reason for having two different versions of part or drawing. When file is not checked out from vault it should NEVER be saved. We pay hell lot of money for Inventor subscription every year and what do we get? Just piece of sh!t. If Vault developers can’t understand such basic thing, then you should fire them, because you don’t need such incompetent idiots in your company. I heard former Autodesk CEO Carl Bass on some Autodesk event, talking about having ping pong tables in company in order to create “creative” atmosphere. Well at least we know where our money goes – table tennis tournaments. Too much is simply too much. I absolutely don’t care about the reason behind this, whether it is migration of the file, updating physical properties or whatever is going in the background. Vault should handle this and not the user. I used PTC Creo and SolidEdge in my previous jobs, and this never happened. File was not saved, period. Is this so hard to understand? If you have assemblies with hundreds of parts, subassemblies etc., constantly being opened and closed during a day, it’s virtually impossible for human being not to make a mistake during saving. Moreover, it appears even on parts that I didn’t touch. Instead of showing this message, simply don’t save the file. No wonder many users are switching to competitors. Their developers are probably different level. You can’t make a simple button work properly.
@martin.halacek wrote:Write enabled – not checked out from Vault. Again, again and again after all those years. I’m on 2022 and I’m really pissed. How many years we have to wait until Autodesk solves this issue. Another decade? We have constant problems with unwanted overwriting of our files. Vault can’t do basic thing that it is intended for. There is absolutely no reason for having two different versions of part or drawing. When file is not checked out from vault it should NEVER be saved. We pay hell lot of money for Inventor subscription every year and what do we get? Just piece of sh!t. If Vault developers can’t understand such basic thing, then you should fire them, because you don’t need such incompetent idiots in your company. I heard former Autodesk CEO Carl Bass on some Autodesk event, talking about having ping pong tables in company in order to create “creative” atmosphere. Well at least we know where our money goes – table tennis tournaments. Too much is simply too much. I absolutely don’t care about the reason behind this, whether it is migration of the file, updating physical properties or whatever is going in the background. Vault should handle this and not the user. I used PTC Creo and SolidEdge in my previous jobs, and this never happened. File was not saved, period. Is this so hard to understand? If you have assemblies with hundreds of parts, subassemblies etc., constantly being opened and closed during a day, it’s virtually impossible for human being not to make a mistake during saving. Moreover, it appears even on parts that I didn’t touch. Instead of showing this message, simply don’t save the file. No wonder many users are switching to competitors. Their developers are probably different level. You can’t make a simple button work properly.
This seems like a bug. They happen.
I have never experienced this kind of behaviour with Vault.
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")