Part replace in assembly file is locked vault prompt

Part replace in assembly file is locked vault prompt

Tony_Yates
Advocate Advocate
177 Views
3 Replies
Message 1 of 4

Part replace in assembly file is locked vault prompt

Tony_Yates
Advocate
Advocate

Hi Guys,

 

Strange behavior on one of our machines.

Works perfectly on all other machines.

Inventor pro & vault pro 2024.3.1

 

We have an ilogic rule to start a new frame generator assembly.

It creates an assembly asks you to save, inserts a template part and replaces that part with a new one based on what you saved the assembly as.

 

On this one machine when replacing the template part it gets a vault prompt saying the file is locked.

 

The files are not even in vault at this stage.

The replaced part says it is locked but if you look at the properties it is not locked.

In the vault browser window in inventor it shows a ! in the white circle and says it is locked.

If you hit the refresh button it fixes the issue and puts the green cross to show it is not in vault yet.

 

Any ideas why this is happening?

As I say it is only one this one machine.

 

cheers,

 

Tony

 

0 Likes
178 Views
3 Replies
Replies (3)
Message 2 of 4

daltonNYAW9
Advocate
Advocate

The exclamation mark in the circle means inventor doesn't know the file's vault status. You said refreshing fixes the issue, try adding the refresh command in your code. I think this is it....

ThisApplication.CommandManager.ControlDefinitions.Item("VaultRefresh").Execute

 

0 Likes
Message 3 of 4

Tony_Yates
Advocate
Advocate

Thanks for your answer, but it doesn't answer why this is happening.

Yes I can add this to my rule, I would also have to tick the box don't show this ever again on the prompt.

I am more interested in why it is prompting and again only on one machine.

 

cheers

Tony

 

0 Likes
Message 4 of 4

daltonNYAW9
Advocate
Advocate

This might be a better question for the vault forums.


These are issues ive had that are simmilar...
The file has model states and the 'active' model state is different than the one vault recognizes (idk how model states work w/ vault)

Have the user delete their local copy and re-get the file

Check if the user has different permissions

 

0 Likes