Get vs Open from Vault

[johan.degreef]

We work with 1 project file.

I want a complete folder from the vault on my local workspace for editing.

What is the difference between:

"Getting" a complete folder from Vault with the Thick Client or

Open from Vault with the Inventor Vault Add in?

If I do a get, I see the folder on my C drive, but I cannot open that folder from the Open from Vault...?

[gandhey · Accepted solution]

Hello,

Get from the client is just the downloading the files / of seleced folder to your local working folder.

Where as 'Open from Vault' will download the selected file (along with all its references) to local and open it in inventor

I didnt quite get your last comment : you can not open the folder with Open from vault command. 

Regards,

Yogeshwar

(Vault team)

[johan.degreef]

Well if I "get" a complete folder, it is in my local workspace.

If I do an open from Vault, I cannot get to my local workspace. Then I just use the normal inventor "open" command...?

[ihayesjr · Accepted solution]

---

@johan.degreef wrote:

Well if I "get" a complete folder, it is in my local workspace.

If I do an open from Vault, I cannot get to my local workspace. Then I just use the normal inventor "open" command...?

---

Yes. "Open from Vault" will only browse Vault for the files that you want to open. It doesn't browse your local workspace. Hence "Open from Vault".

"Open" will browse your local workspace.

If you find yourself starting the "Open from Vault" dialog, you can switch it to view the local workspace but clicking the button "Open a file from local" as shown in the image below.

The reverse is possible also. If you are in the "Open" dialog, you can switch to viewing files in Vault by clicking the "Browse to a file in Vault and open it" button as shown in the image below.

[johan.degreef]

Many thx @ihayesjr @gandhey 

[cstarker6VCG4]

This is wrong. Opening will not download the file and overwrite the out-of-date local as it should if the file is already present on the local. This is not correct behavior, of course, because the local means nothing if the file is not checked out.

Our engineers have constantly been seeing deprecated file versions when opening assemblies from Vault. The local and all dependents should automatically update/refresh on open. I posted about this but Autodesk's response implied this was intended behavior, profoundly disturbing if true. I opened a ticket regardless because a version-control application that can't version-control needs to be dumped.