Why does my Inventor assembly always need updating\saving when there has been no change to it?

This is a question that comes into Autodesk Support frequently. One reason might be that it comes down to how Inventor resolves (finds) files.

A popular practice is that more than one project file is used in the Vault. Maybe it was considered an appropriate workflow to place IAM's into a library folder. This does cause this problems though.

One way to explain it is as follows

In Inventor, using the Library.IPJ, the Assembly refers to an IPT

 When Inventor tries to find the file it first looks at the "Location" (Workspace) plus the "Subfolder Path" (Assembly Folder\Subfolder).

BUT, and it is a VERY BIG BUT, when you switch to another project file called Designs.IPJ for example the following change happens.

 

When Inventor opens the Assembly, it looks in the "Location" plus the "Subfolder Path". Now, the last time the IAM was opened, it knew to look in the "Workspace\Assembly Folder\Subfolder" folder. But the file is not there. Instead it is is in the Location  = "Library1" folder and subfolder "\Assembly Folder\Subfolder".

The difference is easier to see when compared together like this.

• "Workspace\Assembly Folder\Subfolder" (Library.ipj)
• "Library1\Assembly Folder\Subfolder" (Designs.ipj)

So, just changing the IPJ can change the file!

At this point, Inventor initiates its file resolution algorithm and goes through a series of steps to find the file. If you are logged into Vault, you will see a message saying that "Files are missing from your workspace. Would you like to open the database to resolve the component?"  The precise wording in the message changes depending on the release of Inventor you are using.

Believe it or not, this is a Vault feature.Vault is telling you that something has changed and you better do something about it! What causes confusion is that, if you click "No" Inventor then goes on to actually find the file.( because the message pops up before Inventor goes through its algorithm to find files.)

However, if Inventor fails to find the file, it will display the file resolution dialogue box.

So, for this reason I would:-

1. Never suggest it is a good idea to put IAM's into Libraries.
2. Never have more than one IPJ in the Vault
3. Always put the IPJ at the root of the Vault
4. Always follow the best practice for setting up the Project file.


UPDATE 2/8/2011

If you really must check assemblies into the library that might later need editing you will need to check the Library IAM out, and check it back in using a project file that has the library subfolder defined as a library and not the Workspace. In other words, follow this workaround.

For Editing Assemblies in Libraries.
1. Activate the Library project from <Path>\Libraries.IPJ
    1.a) Which has the workspace defined as .\Libraries
    1.b) Mapped to the Project root to $
2. Check Out the assembly and Edit, Save (saved under Libraries) but DO NOT CHECK IN
3. Activate the Designs Project from <Path>\Designs.IPJ – THIS PROJECT SHOULD BE USED FOR CHECKING IN EDITED ASSEMBLIES.
     3.a) Which has the workspace defined as .\Designs
     3.b) Mapped to the Project root to $
4. Create a Phantom assembly and place the Library assembly (This may not be necessary if the Library assembly does NOT have iParts or Sub Assemblies)
5. Tools > Rebuild All and Save All the files in Libraries.
6. RMB on the Library assembly and Check In.

Comments

[Theo Bot]

Dear Richard,

If you use one projectfile. it's hard to change the librarie components.

How would you suggest to do that. The way by moving in the vault is not a great option.
In most cases I create a ipj file in the library folder without a relative workspace.

Kind regards,

Theo Bot

[Richard]

Hi Theo, The design concept behind Library files is that they should never change. If there is a likelihood that they will be changed, they should never be placed in the Library folder. One way to do this is to store them in a Non-Library Folder underneath the workspace and call it "Standard Components" or "Purchased Components" for example.

If, for unforeseen circumstances your Library files do need to be changed. A copy of them can be made with new file name.

I hope that answers your question.

Richard

[Cory McConnell]

So, Richard, your telling us that Library files will not need to be migrated with every new release of Inventor?

Just so everybody is aware, having a single project file in a Vault is not going to solve the problem of Inventor needing to save files that are seemingly unmodified. It may help, but it will not solve the issue.

I have a single project file in my Vault, and I am frequently faced with this HUGE issue.

Cory McConnell

[Richard]

Hi Cory,
Thanks for the response. To answer your question, you are right. Since a hotfix in the Vault 5 timeline, library migration is not forced by Vault (provided that they were last saved in Inventor 5.3 format (or later)).

I agree, having a Single vaulted project is not the whole story. There are other reasons. I am trying to go through a process of analysing, documenting and publishing the root causes on this blog, as they get reported to me. All the posts I think are relevant can be found under the blogs "Files Resolution\Updating" Category. If you (or anyone) has any experience to share, or articles that you want me to add, I am happy to publish them here.

[John Kavusak]

Autodesk

Hi Richard

This message should go to product designers/developers of the Vault product line.

When will the vault product evolve so user permissions in the vault will allow a select group of users the ability to change library files. If the product worked this way, there would be no need for this library.ipj file. If you say that files in the library should never change then you have been removed from industry way to long. Library components change all the time and if these are purchased parts, then these changes are out of the company's control.

Also, lets let the vault Workgroup and above do their job on these files and manage revisions of these library files. That is the correct way to control change. If a manufacture of a component makes a change we want to see that Revision history, we don't want to have to manually keep track of 10 copies of a library component.

Also if there is an item assigned to the library part, how is this problem resolved? If I can use the library project and I cant move the file out of the library then I'm stuck.

I think Autodesk needs to take a good look at the real world. Autodesk has been living for too long in their perfect world sandbox. These are issues that everyone of our customers complain about.

JK

[Richard Rankin]

Hi John,
If you have a message for the Product Designers, then logging wishes on the product feedback site is where you need to go...

http://usa.autodesk.com/adsk/servlet/index?siteID=123112&id=1109794

[Alfredo Tobar]

Hi,
What could be the reason that there is a newer version in the C (local drive)?

Somme times, vault give us this message: File: C.... is newer that the last version in the vault. Are you sure you want to replace it with te version in the vault?

Thank you .
@