topic Re: Model states and Vault-ing files in Inventor Forum

Model states and Vault-ing files

Goran.Kis. — Mon, 22 Nov 2021 14:21:49 GMT

Hi all,

we have situation and maybe someone have idea how to solve this.

I will be short...

File with Model State have only active Model State physical properties updated, but if you link in assembly other non-updated Model State than you will need to update those Model States routing physical properties... That is clear but....but...

if you Vault files with, for example, Master Model State active and physical properties updated and, for some other assembly, you choose different model state it will ask you to update physical properties for that Model State route. But what if that file is locked and released with all drawings with Master Model State (or any other)? Then all files with linked Model State route that is not updated becomes "dirty" and it cannot be unlocked only if you make new revision (witch is not acceptable).

For what i have noticed you don't have physical properties for all model states unless model state is active and save as active.

Am i wrong or doing something wrong?

Thnx.

Goran

Re: Model states and Vault-ing files

Gabriel_Watson — Thu, 25 Nov 2021 21:43:02 GMT

I guess Model States do not change the fact that, just like in LODs, you should be updating all Model States before saving, checking in, and releasing the file in Vault.
If you leave a non-updated Model State in any file, then open that pandora box later on, Inventor will be very thorough and ask you to update your released files to account for those changes. You're technically dirtying the file on purpose (so it is not as much of a bug as it is a reckless workflow, even if it is elusive to keep that in mind).

One way to avoid new revisions is to select one file at a time in Vault and perform a State change rollback, then re-release as the same revision. Although you would not want to do that often, or have everyone know about this tool.

Re: Model states and Vault-ing files

Goran.Kis. — Thu, 25 Nov 2021 23:19:04 GMT

Try to create simple file with model state 1 and model state 2.

Update mass and save model state 1, go to model state 2 and update mass and click save. Now go back to model state 1 and tell me what is the mass? It is N/A. If you update mass and save then model state 2 mass is N/A and now we have a problem....

Re: Model states and Vault-ing files

Gabriel_Watson — Fri, 26 Nov 2021 05:58:16 GMT

Alright, I can verify that. But testing in Inv. 2020 the same happens with View Reps in a part, and similarly with LODs in an assembly.
I will have to test it out in Vault to see if there is any significant problem, but at face value I agree it seems weird that is the behavior. I just don't see any difference to my 2020 install yet.

Re: Model states and Vault-ing files

swalton — Fri, 26 Nov 2021 21:01:54 GMT

My understanding was that Vault supports Lifecycles for Model States using Items.

Are you using File-Based or Item-Based Lifecycles?

I think that using more than one model state per ipt/iam will require a change to Items. I'm not on 2022 yet, so I can't test it.

Re: Model states and Vault-ing files

johnsonshiue — Fri, 11 Feb 2022 21:57:09 GMT

Hi Goran,

I think I know what you are seeing. To have the mass prop persisted on a per Model State basis, you will need to consume the Model State in a drawing or in another assembly. Try the followings and you will see it should work.

1) Start a new assembly.

2) Place the component in different Model States.

3) Update the mass of the top-level assembly -> Save. Make sure the subcomponent is saved.

Now you can open the subcomponent, activate each Model State and check the mass. The file should not be dirtied.

Many thanks!

Re: Model states and Vault-ing files

Goran.Kis. — Tue, 15 Feb 2022 12:09:39 GMT

Hi @johnsonshiue and thnx for replaying.

I have try and it doesn't work.

I have attached test models here.

Thnx,

Goran