Vault workflow - dirty files

[-niels-]

Hey everyone, i'm still pretty new to Vault workflows from inventor so i was wondering:

What are common reasons for files to be flagged as "dirty" (in need of saving, have an * after their name, etc.)?

I've been having a little fight with one of our assemblies and i'm suspecting that a component (sub-assy) that is set to "flexible" is causing problems and i'm still in the process of correcting this.

It would be helpful to have a better idea of things that might cause it to require saving all the time even though the the sub-assy on itself is behaving properly.

Sort of a list for me to check off.

[-niels-]

*sigh* the addin isn't the cause...
I tried the "Faulty_assy.iam" on my work pc again, with the addin active, and after saving it behaved properly like you've been seeing...
So my test assembly isn't displaying the same behavior as my actual assembly.
I'm at a loss now, i'm going to pack&go the actual assembly and share it with Autodesk in hopes they can see what's going on... 😞

[Mhawker]

Do you have "Prompt for save for re-computable updates" checked? Application options, save tab.

[-niels-]

Hello Mhawker (and welcome),

I do not have that checked, never had.
Checking that would probably make it worse in my case...
Or do you think it should be checked?

I've sent my original files to Autodesk and they found the same behavior that I'm seeing, which is different from the files i attached here for testing.
It's been sent further up, to development, and I'm waiting to see what they can find now.

[Mhawker]

I had always had this checked in the past when using single user projects.  Now with some company changes we are using vault, new custom templates, a custom Add-in and flexible assemblies.  We added many new variables all at the same time which seem to be causing similar issues to you are experiencing. I'm just tryed out diableing that feature to try and solve my problems, but it was unsuccesful.  Please post an update if your support ticket yeilds any results.

Thanks,

Mike