Vault Error from Inventor "(#) dependent files must be saved..."

[kennyj]

In Inventor, when trying to check in an assembly, you may get the error message attached.

At this point, no files are checked in until the mystery dependent files are found and saved.

My idea is to have all possible files that can be checked-in, do so with an error message at the end that states the names of the files NOT checked in due to the need to be saved, etc.

Why this is an issue, is the dependent files listed can be (1) not checked out from Vault, so they cannot be saved by the "save and continue" option offered and/or (2) may be locked files from Vault that were used for reference and cannot be checked out/in, etc.

Currently you cannot Check In any work until this is resolved, so the idea of checking in all eligible files FIRST then letting the user know there are files to check hopefully makes sense enough for you to vote to support.

See this post for similar: https://forums.autodesk.com/t5/inventor-ideas/items-to-be-saved-on-check-in/idc-p/7122025#M18690

Thank you,

Kenny

[ihayesjr]

In the Vault Browser, select the Filter icon and select With Unsaved Edits.

[kennyj]

Thank you @ihayesjr,

But I believe this filter will show files that have not been saved.  The issue we have is, some files cannot be saved (they are locked in Vault and unable to be checked out).

So knowing the files that cannot be saved still does not help get the files you want to be checked in, checked in.  Please let me know if I misunderstand.

Thank you!

Kenny

[Anonymous]

A single file out of tens is blocking my progress...

How about showing which dependent file/s need to be saved?

I'm having this problem and not knowing which file is preventing me from checking in the entire assembly is annoying to say the least.

[kennyj]

@Anonymous,  hit the double arrows at the bottom right of the "Dependent(s)" error screen to see the file.  This does not solve the issue if the file is not checked out (still cannot save) and worse, if it is locked (so you cannot save even if it is checked out).

This becomes a problem if you are using library parts that have not been migrated and are locked; you cannot update them and cannot save, so you have to do a work-around just to Vault your project.

[Thomas_Helm]

@Anonymous, during our Vault migration from 2014 to 2017 we identified library files in version 2009. Such files was first migrated direct to 2017 with the hope that the "dirty flag *" disappears in order to Vault our main assembly . Unfortunately, the "dirty flag *" appears also for migrated files, when the previous version was 2009. At the end, we was able to solve the "dirty flag *" issue while migrating the 2009 files first to 2014 and than to 2017.

[kennyj]

Thank you for the commnet @Thomas_Helm. 

Migration is only a small portion of this issue.  Files locked by other users, locked as library parts, etc. will stop you from being able to Vault a project.  Files that are older version and need to be migrated stop the vault check-in process, files that have outdated properties, missing/old styles, etc. 

So if you open an old file, make a change to the assembly and try to check it back in, you will get a message about X dependents requiring a save before Vault Check in.  If ANY of those dependents are unable to be checked out / saved, NONE of the files will check back in.

[Thomas_Helm]

@kennyjI assume that Autodesk Vault want to store as much as possible "clean" data within Vault as following actions like assign item/copy design will use the information in Vault which are updated during the checkin. So if the assembly is not updated correctly, it will also not update the references in Vault (behind the scene). I guess to avoid future issues, they block the checkin at all until the referenced files are OK. But this is just my interpretation 🙂

[kennyj]

Hi @Thomas_Helm,

Not to start a debate; but you cannot open any file in Inventor (for example) without it wanting to "update".  So if you open a file, save it and open it immediately - it will ask you update the file; even though no changes have been made.

The problem is NOTHING will check-in with the current process.  I don't mind it warning that certain files were not able to be checked in or similar, but to cancel the check-in and prevent the new work from being placed in the Vault is almost on the verge of being a bug/flaw.

If you assumptions are correct, then another solution would be to fix how Vault defines "clean" data.  A file I didn't check out, can't save and didn't change should not prevent me from checking in a file that references or uses that file.

[Anonymous]

It's amazing to me that this hasn't been solved yet.  We have been having the issue for years and nothing seems to change.  At one point, all of our users got into the habit of selecting "Yes to All" when doing a check in and being prompted to save umpteen files.  What ended up happening, somehow, is that library files (yes in a Project driven library location) would be updated/saved and checked in.  This would cause all kinds of issues, especially with iParts because every other user's local library was constantly out of date.  We created a fictitious user and this user checked out the entire library to avoid this from happening.  Now, however, when these "dirty" library parts are included in an assembly, the assembly cannot be checked in initially unless adding the file to the Vault FROM the Vault.  Then, more often than not (but not always) when you close the file and it asks if you want to check in, you can say yes and it will check in.  If you try to check in from the browser or thru the Vault/Check-in button, you get the 'Assembly Name' and (#) dependent files must be saved.... error.

[bradeneuropeArthur]

Today still not solved!

[bsnyderACLUW]

Been running into this issue lately...... We really need a fix for this!!! The only thing I cannot check in is the assembly itself. all parts have been checked in and library parts have been updated. I even get the nice blue + sign next to my assembly name letting me know it has been saved (and the green check mark). yet I still get the same pop up that is described in this forum.

[bradeneuropeArthur]

Hi, Hope that this will get solved soon. Question? am I alone if I am wondering why only a few of us (Vault users) are complaining about this behavior in Vault? I am struggling with the the idea that we need special Inventor workflows to avoid problems with dirty files. Vault does not help us at the moment, but it is blocking us in some kind of way. We need really a lot of additional time to create our designs that can be checked in and released. But we cannot go back easily anymore..... Often production (External) makes mistakes because they are waiting for a new released version of the manufacturing drawing. Because of the delay in the release process because of the check in failure, manufacturing still uses the wrong documentation which results in additional costs for us. Very annoying. This means we are blocked and hindered drastically in our design work because of these unneeded updates. I have frequently asked things related to this in the forum but only with a few results, and thanks for that? Does this mean something? Are those few persons (Vault users) that are using Vault with success in a real other environment then we are in? Is Vault-pro actually used as it is meant to be used or is it often downgraded, as I also often hear? Are only those users that only work with vault and not with a frequently changing design supporting the software? I appreciate your opinions regarding this. Please check my profile about what I have frequently asked if you are curious.

[ihayesjr]

We, at Autodesk, are listening to this request both on the Inventor and Vault teams. There is a long active thread on this topic in the Inventor Feedback Community (Beta forum) about this very topic. Make sure you take a look at that thread and the changes in Inventor that have been changed to help address this issue.

[bradeneuropeArthur]

Thanks for listening and for taking the time to read it. I know what you mean about the topics and we have both already spoken frequently about the situation, I appreciate that. But since you are also only an employee I know that you alone cannot solve the problem that has been there for more then 10 years as far as I know.

[ihayesjr]

@bradeneuropeArthur Are you on Inventor and Vault 2021?

[bradeneuropeArthur]

Yes we are in the testing and implementation phase. We still have the same problems.

[b.mccarthy]

Still an issue in 2025...