In vault explorer for Product Design Suite 2014 Professional, whenever I open a file and choose NOT to overwrite an existing file on my hard drive (a file that is marked as newer than what is in vault). The vault explorer cancels the open file command, and I get nothing. I then have to goto my file open in Inventor 2014 Pro, and manually open the file from my vault working folder.
Is this a bug or is there a workaround?
Hi Jvj,
When you Open a file in VE, it means to open the latest version, if you choose not download the latest one to your working folder, it can't be opened, this is as designed.
In your case, you just want to open the existing one in your working folder, I suggest you in VE, right click the file and choose "Go to working folder", then open files there.
Hope this workaround helps.
I haven't used the 2014 client yet, we are just getting ready to make the switch.
If this is as designed then this is an annoying change. The 2013 client does open a file when you choose not to overwrite the newer version. It continues to open the newer file from your working folder. we should not have to browse to the working folder first.
I think it is better practise to stay in the habit of browsing for files and opening them through VE because it keeps you aware of the file status. I can see that users will end up of browsing for files through their working folder rather than opening it through the vault.
Cheers
Kenny
Go back and read my comment again. The file from vault is OLDER than the file in my working folder. Therefore Vault is in error to choose NOT to open the file because of the discision to NOT overwrite the NEWER file aready on my harddrive.
If the programmers are going to create a new feature, they better work out the old bugs first. Remove the checksum file filter.
We have tracked this issue and will let you know when there is any update.
I would like to make it more clear that we have logged this issue in our system, and we will fix it and make it same behavior with 2013, no target date by far, will update with you when any update.
I am having this same error. I'd prefer it to be the same way as 2013, where it actually made sense to prompt me and continue when I said "No to All". Cancelling the open command is not the right way to handle this.
It is now December 2013, several service packs have been released, and this issue Persists. What is up with that?
Jamie,
This is been fixed in our Vault 2014 Subscription Release 1. If you are on subscription please go ahead and download this from Subscription site.
Thanks!
I am on Subscription, and I do not see a Subscription Release 1 for Vault 2014 in the product enhancements section.
I'm currently running Vault Basic Update 1 build 18.1.8.0, and the problem persists.
Jamie,
The Subscription release is for customers who are Subscribed to Vault 2014 Workgroup and Professional.
Well that sucks!
So the bug is not getting fixed in the vault basic version?
That is just not right!
Yea, I'm on subscription, they fixed the problem, its a very HUGE problem to their system that didn't exist until they changed the code in 2013. They should fix it, and release the fix for everybody. Its not like the program has a different base structure for each version. I've seen the APIs. If anything I think they may be using the paid in Vault users as guinea pigs to test the fix.
They could just roll back that portion of the code, recompile, and release; if the structure is written with proper o.o. code design.
Rant, and Rave, and Rant some more!
jvj
I agree that this should not be just for Workgroup and Professional Subs customers. All customers using Vault (on subscription or not) should still be entitled to fixes that have been changed from expected behaviour in previous releases.
I have a couple of customers who have reported this behaviour in Vault Basic (they are on Subsciption) and find it an awkward workaround to have to go back to their working folder to open the file it seems counter-intuitive for a data management system.
Any chance of this getting updated for Vault basic customers?
Dan
We have fixed this issue also in Base Vault with Vault 2014 SP2. You can get the Vault 2014 SP2 from the following location.