Inventor prompts "do you want to check out this file immediately after a vault check in. Can I make this behavior stop?!"

[ralvarado]

Inventor prompts "do you want to check out this file immediately after a vault check in. Can I make this behavior stop?!"

[BDCollett]

You need to investigate what is causing the file to become dirty. Is there any iLogic triggers running?

[ralvarado]

I have some difficulty believing every file is always dirty.  Six plus years using Inventor and Vault.

All updates are current.

This is a consistent behavior that is just more annoying than important.

[phlyx]

We have seen lots of activity like this.  Save and check an assembly drawing in, including all parts in it.  Then change the state of everything to Released.  Then go to close it and get prompted to save the drawing.  Huh?  And the flakiest one yet, go to Vault, open a drawing that is checked in and released, once it's opened in Inventor click to print the file and get prompted that the file is not checked out and do we want to continue editing.  Huh?  Printing is not editing last time I checked.  

[BDCollett]

---

@ralvarado wrote:

I have some difficulty believing every file is always dirty.  Six plus years using Inventor and Vault.

All updates are current.

This is a consistent behavior that is just more annoying than important.

---

This is a discussion that has been going on for years about Vault and Dirty files. As far as Autodesk are concerned it's working as intended. If it wants you to check it out, it's because something is changing. 

Are there iParts involved? This is a common cause of dirty files.

Without seeing the files involved it's hard to really guess.

[swalton]

I have seen this behavior increase significantly now that we have moved from Inventor 2022 to Vault 2023.2 and Inventor 2023.2.

It happens for some but not all of our assemblies.

I have also noticed significant delays during Inventor 2023.2 save operations on some but not all of our large assemblies.  I am testing Inventor 2023 RTM to see if it is any better.  

[johnsonshiue]

Hi! One particular scenario may yield such behavior. For example, you create a part with multiple Model States. You save the part file and check it in. Then you start creating drawing views referencing a Model State or place the part in an assembly. The part will be dirtied because the Model State is consumed and the local storage (mini file) is created.

Please share the files that exhibit the behavior. I can take a look to understand the behavior better.

Many thanks!

[phlyx]

Hey @johnsonshiue, can totally understand that but with us, when it happens, we check it in, change state to Released, then immediately hit the X to close the file and get asked if we want to save it. No operations or commends took place between releasing the file(s) and attempting to close them.  If I find something it happens with I will try to send a file but it's become muscle memory to just answer No to the erroneous save request.  

[johnsonshiue]

Hi Scott,

When it happens, please try Help -> About -> Ctrl+Alt+D. A small dialog showing the dirty flags will come up. Please take a screenshot can share it here.

Many thanks!

[phlyx]

Will do @johnsonshiue, not my first time digging into what makes files dirty.  Usually ends up being some mass property update or something that means not much to me.

[phlyx]

@johnsonshiue , this is along the same lines.  I opened an assembly I worked on last week.  When I open it I get a message that local copy is the incorrect version for a sub-assembly that is not checked out. 

If I do a get revision it tells me the local copy has been edited and asking if I want to replace it with the version from Vault. 

If I answer no then it still have the local copy not correct version icon.  If I look at what is dirtying the file it basically says it's not dirty.

I did not edit this Friday when I was shutting everything down so not sure what is going on with this and not sure what "changed" so not sure I want to gamble that I'm about to undo something it didn't save. 

Frustrating....  

[phlyx]

And last week had an entire machine checked in and released.  Opened it today and it shows two sub-assemblies it 'thinks' were changed and this is what it says dirtied the files.

There are several assemblies is says are dirty and they all have the exact same traits as this one.  Not sure what is doing that or why but everything was checked in and released Friday.

[phlyx]

Changed state and checked out everything that had an asterisk * beside the name.  Saved everything, checked them all back in and released them.  Closed the top level and closed Inventor.  Opened Inventor and opened the top level from my local workspace (the one I had opened before) and it shows the top level and one of the sub-assemblies is dirty and needs saving.  🙄

 Something is most definitely dirtying the files.  Tried the same thing again and this time I opened it from Vault instead of my local workspace and this time it opened cleanly.  Something is doing this when I open it locally that's not happening when I open it from Vault.

[BDCollett]

---

@phlyx wrote:

Changed state and checked out everything that had an asterisk * beside the name.  Saved everything, checked them all back in and released them.  Closed the top level and closed Inventor.  Opened Inventor and opened the top level from my local workspace (the one I had opened before) and it shows the top level and one of the sub-assemblies is dirty and needs saving.  🙄

 Something is most definitely dirtying the files.  Tried the same thing again and this time I opened it from Vault instead of my local workspace and this time it opened cleanly.  Something is doing this when I open it locally that's not happening when I open it from Vault.

---

No triggers running on any of those sub-assemblies or parts in them?

[johnsonshiue]

Hi! Maybe you want to use Refresh command periodically to ensure the latest files on disc are loaded in Inventor, particularly you have multiple users working in the same set of files.

Many thanks!

[klaaspiet1912]

I have the same problem i am have vault basic  2024 and the latest version of inventor 2024 what can i do 

[BDCollett]

---

@klaaspiet1912 wrote:

I have the same problem i am have vault basic  2024 and the latest version of inventor 2024 what can i do 

---

No known bugs causing files to become dirty currently. Check to see if there is any iLogic running on files.

[johnsonshiue]

Hi! Without seeing the files, I can only speculate. I suspect this is a migration issue. Some of the files may need to be migrated, although migration should not be needed in theory.

Try this to see if it works better. Open the assembly. Go to File -> Manage -> Migrate. Save. There will be many files to check out and save. Then check them back in. Now repeat the old workflow leading the excessive save. Does it work better now?

Many thanks!

[klaaspiet1912]

there ar no ilogic rules running.  a screenshot is ad to the post 

[klaaspiet1912]

here are my files. a have tried today a lot of things but i don't get it