Hi there in the Vault help under moving and renaming files there is the note "All internal dependencies will not be updated until you exit the vault." I am trying to put together some training for our employees and don't 100% understand this statement. Is it recommended that every time you move or rename a file you close the vault before going back and getting the latest version our of the vault?
I want to make sure I give them the correct direction and process to follow when doing training.
I am under the understanding too that files do not get repaired until you do a get/checkout from the vault. Pretty big disappointment here my part regarding that work flow.
Thanks for the help!
In 2012 the file references are not updated in the files at the time of the move/rename operations.
Instead the files are update as they leave the Vault (download, open, pack and go).
Hope this helps.
Yeah, that is what I was gathering. Not a nice solution on our part that is for sure. We use the vault mainly for inhouse storage of our inventor files. Basically to help keep the file relationships tied together. So for example, if you rename a part that is referenced in the assembly. The assembly is not actually updated until you get the latest version of the files?? Do you recommend then that the user checks the assembly out to make sure the updated version is checked into the vault?
At this point with 2011 we just rename the files and it all updates by itself.
There is another senario where at the end of the project I will move the entire folder into an archive folder in the vault. After moving these files, I usually just leave them. Do you suggest that I download them all and recheck them in?
Or third question.... does the update file references command that is new do all this updating for you without having to download any of the files?
I want to make sure I instruct our users as to the best practice for our department.
My apologies I did not explain clearly.
In the Vault we create relationships on check-in that represents the relationships from the file. These relationship are storedin the database. Performing a Move/Rename operation in Vault will maintain the relationships in the database. Your uses/where-used information will still show the relationship between the part and the assembly after a Move/Rename.
Anytime a user does an operation that causes the file to be downloaded the Vault will update the relationships of the local copy of the file to match those maintained in the Vault.
To answer your concern about the user workflow. There is no need to change anything.
Whenever a user Opens or Downloads a file the references will be updated.
The Update References command is a tool used to add some information to the Vault relationships of existing data. You will only need to run this tool on a given file once. We need this information when the files are updated durring a download. Because we require this information to maintain the file references, we block the move and rename operations until that information has been updated. During check-in of new data the information will be added automatically.
Hope this answers your question.
I think I follow you. So even if a part was renamed, the assembly file in the vault that references the old part will now reference the new named part without having to re-check the file in? It doesn't show a new version number or any comments in the vault on the assembly it updated if this is the case which is why I am so confused on the ordeal. Kind of leaves the person up in the air as to if it updated or not. But in reality it is updating and relinking files back to the parent files (if a child file was changed)?
Yes and No.
The file that is stored in our server is technically not updated at the time of the rename.
We store enough information about the relationship that we simply (and automatically) update the references the next time the file is used.
This means that the part file can be moved/renamed infinite amount of times and the assembly will not be versioned.
It also means that when a part file is moved/renamed and is referenced by a large amount files the rename will happen virtually instantaneously.
All of this makes for a much better user experience.
Except for us. Just to get things straight. The assemblies used to update when there was a file rename change. So now you do have to make sure you get the latest version of the drawing and/or assembly to make sure the latest and greatest is the last version checked into the vault if you want to save that change? On our end, we don't just check a couple of versions into the vault when we are at a certain point in the project, they get checked in every day.
You (the user) do not need to update the Assembly or the Drawing as a result of the move or rename (ever). No one can ever see the assembly in a state where it is not fixed. Everytime anyone opens the file, Vault will take over the loading of the children and ensures that the parent will load the child file from its new name/path.
In simple terms, the user does not need to worry about the fact that a dependent file has been moved or renamed, ever, for any anyworkflow.
If someone modifies the assembly at some point in the future (checks-out and makes a change and checks-in) then the parent fille will be stored with the new name/path information for the child. After this point the Vault no longer needs to update the files on open or download.
However, the users will see no preceivable difference in experience for either case.
Sounds Good. Thanks.
I have been using Rename and Move a great deal (on some very large datasets). For the most part, it is 100% better than previous releases. We have not had any broken references. Very happy with the changes.
Access a broad range of knowledge to help get the most out of your products and services.