Inventor saves local files that are read-only and not checked out from Vault.

[MFrysingerKY7R8]

Inventor removes the read only flag to locally updated files that are not checked out from Vault (au...

From the above page: "Status: No issue has been identified and the software is behaving as designed."

Why is this the desired workflow for Inventor?  Every day I open parts, assemblies, drawings, etc. that I want to look at or make temporary changes that I do NOT want saved.  I know these files are read-only.  I know these files are not checked out of the vault.  If I open a read-only flexible assembly saved in vault and move a piece, it should not create a locally modified saved file that is different from the vault.  WHY does Inventor save these changes locally without the files checked out of the vault?

I constantly end up with assemblies littered with "Locally modified" green bubbles on the vault status window as well as changes made to local files that end up causing issues when Inventor shows me things that should not have been saved.  This then causes issues in manufacturing when what I'm seeing on my screen does not match the files and drawings that are in the Vault.  What is the purpose of having read-only files if Inventor ignores it completely and saves anyway?  Even worse than this is when I do see a file is locally modified, if I do a "refresh" on that part or assembly it sometimes doesn't even fix it.

If I have an assembly open with nothing checked out, and I close Inventor and reopen it, I expect things to be reverted completely back to their original state.

[CGBenner]

@MFrysingerKY7R8 

Hello and welcome!

The document you linked also states: "At this point if user saves the assembly through the Inventor Save command Inventor will remove the read-only flag to the child..."  This makes me think that you have to purposely hit the Inventor Save button for this to happen, after being given the Check In warning.  Are you saying that this is not true, and that Inventor saves the file as changed without explicitly using any Save function?

[MFrysingerKY7R8]

Yes, I use the save command.  I often work in assemblies with dozens of subcomponents that are read-only, so I want to save the changes to the assembly I'm working in, the components I have checked out (or are newly created), and not the child components that are not checked out but have been locally modified.

For example: a pneumatic cylinder subcomponent that is flexible.  If I open that subcomponent and move the cylinder, it prompts to edit a not checked out file and upon save defaults to locally modifying that file.  If I'm working in an assembly with dozens of components I don't want to have to scroll through that prompt and pick out the read-only files every time I save.

[CGBenner]

@MFrysingerKY7R8   Something about this doesn't sound right.  I'm going to tag in @johnsonshiue who might have some more insights here.

[BDCollett]

There should be an option to NOT have Inventor remove read-only regardless. This does happen, and people end up with dirty assemblies because some users have made changes to local files that were never checked out from Vault, but the top level was checked out, so the IAM expects those modified files.

From my testing the removal of read-only on files is a bit inconsistent as well. Sometimes it says NO, other times it gives options to remove read-only. It should not be an option when using Vault in my opinion.

[pball]

Just to chime in, making an edit on a checked in Vault part and selecting no to checking it out and then doing a save on the assembly it is in yields this. As I just saved before testing this, the read only part I edited is the only thing listed. It would be nice if parts that are not checked out could be set to No to save by default. I believe that would get around the issue being described in this thread. This would at least require a user to intentionally save a not checked out part they edited, instead of accidentally saving it along with parts they do want to save.

[johnsonshiue]

Hi! I took a look at the article and the defect PDM-34126. It was indeed closed As Designed (per Inventor). However, I am not yet able to reproduce the behavior without using Vault. Can anybody offer a workflow showing the exact behavior just with Inventor (no Vault)?

Many thanks!

[MFrysingerKY7R8]

I'm not sure what you are asking for?  The main issue here involves the use of vault.  Inventor should never save over any local files if the files are in the vault and not checked out.

[BDCollett]

---

@johnsonshiue wrote:

Hi! I took a look at the article and the defect PDM-34126. It was indeed closed As Designed (per Inventor). However, I am not yet able to reproduce the behavior without using Vault. Can anybody offer a workflow showing the exact behavior just with Inventor (no Vault)?

Many thanks!

---

This whole issue is Vault related. Inventor does not check read-only with-out Vault (or the old legacy method which I hope no one still uses).

Inventor should not be able to override the read-only on files like it is, there is no scenario where this is useful. If you absolutely have to you can un-check from Windows explorer. 

[johnsonshiue]

Hi! My point here is trying to take Vault out of the equation, so I can reproduce it just using Inventor. So far I have not found a workflow that Inventor overrides a read-only file without informing users.

Many thanks!

[swalton]

@johnsonshiue 

My understanding of the issue is that Inventor is overwriting files controlled by Vault.  The Inventor-Vault interaction is the heart of the concern.

I understand that the behavior is as-designed by the Vault and Inventor teams, but it seems odd to users when they lock a file in Vault (because it is not checked out and they don't want to keep changes) and Inventor is allowed to save modified copies to the local workspace. 

[BDCollett]

---

@johnsonshiue wrote:

Hi! My point here is trying to take Vault out of the equation, so I can reproduce it just using Inventor. So far I have not found a workflow that Inventor overrides a read-only file without informing users.

Many thanks!

---

As discussed, it does inform and give you an option. It shouldn't give the option at all is what we are trying to convey.

[MFrysingerKY7R8]

You are correct, Inventor does inform the user when it wants to save over a Vaulted read-only file to create a locally modified copy.  Our point here is that this workflow is NEVER useful.

The Vault is called a "Vault" because it is used for safe storage of documents.  When would it ever be useful to have a file saved in Vault and allowing machines to locally save over those files and create uniquely different files than what is stored in Vault?  It makes no sense.

It is especially frustrating when working in large assemblies creating a new design.  I will often have dozens of files checked out, dozens of new files being designed, and dozens of read-only files in the assembly I'm working in.  When I hit save, Autodesk expects me to scroll through a list of 50+ files every time I save in order to pick out read-only files and tell Inventor to NOT save over them?  Insane.

[BDCollett]

We might have to make a demo video to highlight this issue.

[MFrysingerKY7R8]

I just created a new part, PM56793, saved it, and checked it into Vault.  I then placed that new file in an assembly and saved the assembly.  I cannot think of a possible reason why this would create a locally modified file for a brand new, untouched part... Yet Inventor did it.

[johnsonshiue]

Hi! This behavior does not make sense to me. Does the exact ipt file exist in your Vault folder on your local drive after you check it in? Is the Vault folder a local drive folder or on a shared network drive or a cloud drive?

Many thanks!

[BDCollett]

---

@johnsonshiue wrote:

Hi! This behavior does not make sense to me. Does the exact ipt file exist in your Vault folder on your local drive after you check it in? Is the Vault folder a local drive folder or on a shared network drive or a cloud drive?

Many thanks!

---

I will create some videos highlighting the issue. The green dots that should not exist cause a lot of confusion. Especially if the files are released and locked.

I would hope no one is using a Network or Cloud location for their local Vault files, that is certainly not the cause from what I have seen because most know better than that.

[johnsonshiue]

Hi Ben,

We do have users mapping their Vault folder to a network shared drive or a cloud drive. Some people want to bypass the check-in/check-out process. Also, it might be a way to have multiple users "collaborating" on one Vault.

Many thanks!

[MFrysingerKY7R8]

Yes, I checked it in and did not check "Close files and delete working copies" so the file is still on my C:\ in the Vault project folder.  No, the Vault location is not located on a cloud or network server.  It is in the root directory on our C:\ drives.

[BDCollett]

---

@johnsonshiue wrote:

Hi Ben,

We do have users mapping their Vault folder to a network shared drive or a cloud drive. Some people want to bypass the check-in/check-out process. Also, it might be a way to have multiple users "collaborating" on one Vault.

Many thanks!

---

Johnson, sorry but the sentence you wrote here has me wondering if we are even referring to the same thing when we mention "Vault".

I deal with a lot of Vault users, I would never see anyone bypassing the check-in/check-out process, that seems to defeat the entire purpose of using Vault to begin with.

I don't understand the multiple users "collaborating" comment either. That is what Vault does.

The beauty of Vault is that it uses your local drive when working on files.