Inventor 2020 - can't refresh part from Vault?

[PatrickCampbellCoral]

I can't seem to get the latest version of a model from the vault. The refresh file is grayed out and 'get revision' won't actually grab the latest version. Same thing with 'revert to latest'.

I essentially downloaded a STEP file from McMaster, it opened in a new Inventor 2020 instance. I saved the file, checked it in. Went back to my model, inserted the new part, realized it should be brass, so I went back to the other application, checked it out, changed it to brass, checked it in. Closed that application.

In my assembly, cannot get the assembly to pull the latest file from the vault. This used to work in previous versions. I'm using Vault Professional 2020. All latest patches and such. 

Capture.PNG

[gandhey]

Hello,

Looking at the snap provided, there is actually nothing to 'Refresh file'. Please see the Vault status icon on the file - it is White circle (indicating this is the latest file from vault) with an asterisk (indicating there are some changes on this file in the same inventor session likely).

This command 'Refresh File' is available when the file in Inventor session has non-latest changes than Vault.

Sorry but I am not sure what you are comparing this behavior with.

Regards,

Yogeshwar

(Vault team)

[AlexZW28B]

I am using Inventor 2020.3.2 and also having similar issues - all the time. I have a part that I modified in the assembly without checking out the part - intentionally to just see if something would work, and when I try to "refresh file" it spins the circular windows loading icon, and then nothing changes... I then have to close my whole model, go to vault folder, do a get on that file, and then re-open assembly. I know for a fact the file has changed, as I did change it. Upon closing the file after changing it, Inventor notifies me that the file has changed, and asks whether or not I want to save the changes - so of course I select no... However, because I have the assembly open where that component was used, it still retains the memory of that original change I had done... I now want to refresh or re-get the file... and it doesn't work - at all - from my experience now...

I have included some images showing that the part requires a rebuild - due to my change, and that the vault shows the file as modified - due to the asterisk on the vault view beside the file. I do not have the refresh file option - However, if I use the assembly tree and select rebuild from the RMB menu on the tree item, I can then send a refresh command - just nothing changes...

[johnsonshiue]

Hi Alex,

There could be some misunderstanding of how Refresh should work. Refresh command compares the file currently loaded in the memory and the one on disk. If the one on disk is newer than the one loaded in memory, the Refresh command will load the newer file (unloading the one in the memory and also wiping out any unsaved changed).

This behavior facilitates collaborative workflows.

For example, UserA opens an assembly with a bunch of parts. He checks out and edits the assembly and a part. UserB checks out another part in the assembly. He makes some edit on the part and checks it back in. UserA can sync to UserB's change and run Refresh to ensure the file is up-to-date.

If there is no difference between the file loaded in the memory and the file on disk, Refresh is a null op.

Many thanks!

[jbm]

Hi Johnson,

I have same issue with Refresh. Even after getting latest file version and forcing to overwrite local file, the refresh command is not updating.

Did a small screencast without audio though

https://knowledge.autodesk.com/community/screencast/a54c5b8c-fb04-40a1-b3ee-a7732d20c142

[johnsonshiue]

Hi! Many thanks for sharing the recording! If I understood the workflow correctly, I would say Refresh would not make a difference in this case. Refresh compares the file time stamp of the file you open in Inventor (memory) against the one on disc. In your case, the file on disc remains unchanged. As a result, nothing is refreshed.

To refresh, you will need to get a different version of the file on disc. Then Refresh command will reload the file from disc to the memory.

Thanks again!

[imarandet]

Hi @johnsonshiue 

I might be wrong, but it seems that what you explained here is not the same as what can be found on the Vault Help pages:

https://help.autodesk.com/view/VAULT/2022/ENU/?guid=GUID-DE878647-513B-4235-AC63-B662CE6670D3

My understanding from the help is that the file is compared with the Vault content and if not up-to-date it is retrieved from the Vault.

It is not mentioned that the file in memory is compared wth the local one.

[johnsonshiue]

Hi Isabelle,

I double-check with our expert regarding my prior statement. In terms of Inventor Refresh command (File -> Manage -> Refresh), the description is correct. Inventor checks the time stamp of the loaded document against the one on disc. When the one on disc is newer, it will be reloaded.

Vault and Vault Add-In has another command called Refresh Files. It behaves exactly as described in the Vault Help. So, Inventor Refresh and Vault Refresh Files are two different commands and they behave differently.

Many thanks!

[Jim.RX4GE5]

I'm having the same issue. Saying yes to the dialogue boxes that tell you "you are altering a file and your changes will not get saved to the vault" changes the file and causes the file to have the asterisk beside it in the vault tab. When you save the assembly, the dialogue box comes up with all the files inventor wants to save, select "no to all" except the assembly.

Inventor/vault-add-in then seems to get stuck.

The altered files are saved in the assembly memory, but not saved on disc. From what Johnson said this doesn't change the time stamp and when vault add-in compares the files it then cannot refresh the file. 

If you open the files you are wanting to refresh in a separate inventor session they appear as they are supposed to, up to date and synchronised with vault.

It seems the assembly is holding on to the past.

I'm sure it can be fixed with closing the assembly and reopening from vault, or (force) over writing components from vault and then opening assembly...but my assembly has 109000parts in the current LOD and it takes ages to do so. 

The normal behavior of refreshing an out of date part from vault with the add-in works fine, if you haven't made an out of turn edit.

[kgentnerHV352]

I'm having a similar issue while working with Vault at work, here I'm working on the top assembly of a project, and this top assembly has three large sub-assembly files. My coworker told me he checked out one of the main sub-assembly models, updated the file, and then checked it back in from Vault. Unlike the original post, I can see that refresh is needed (CIRCLES ARE FULLY SHADED GREEN) next to the main sub-assembly file my coworker updated and the top assembly file I currently have checked out. I am wondering why when I right click all options are "grey'd out" and it won't let me refresh the file.

I could see something about it already updating on my local so there is no need or a similar explanation but when I delete the main sub-assembly file my coworker updated from my local drive, and open it through Vault client, the top assembly file I currently am working on updates with the latest version of the main-sub assembly file my coworker worked on.

Does anyone have an explaination of what's going on? And sorry if this was wordy and confusing wrote that in one shot after a lot of caffeine lol.

[CGBenner]

@kgentnerHV352 

Hello, and welcome to the forum!

Are you and your coworker both using the same Inventor Project file?  When your coworker checked the assembly back in, did they fully check it in?  Or did they use the option to check the files in and leave them checked out locally? (Which is a way to upload changes to Vault on a file you intend to keep working on)