I have a drawing that consistently references an old version of a part file. When I open the drawing from Vault, it pulls in REV A instead of the latest, REV B. This gives me the 'triangle' glyph beside the part name.
To remedy this, I have tried to 'Get Revision' by right clicking on the file in the Vault browser bar within Inventor. After I 'get' the latest rev, I perform a global update by clicking on the lightning bolt with the plus sign. Then the drawing updates to the correct geometry.
I check the drawing file back in, but next time I open it I see it references REV A of the part.
Does anyone know how to force the drawing to reference the latest Revision?
After getting the latest version of the Part and updating the drawing, did you save the drawing and check-it in? Also can you please check the version that the drawing is using when you use "Get/Check out" command on the drawing in Vault Explorer client?
Yes, I can save the drawing and check it in but it still references the old version of the part when I open it.
I have discovered that this is not an issue when I open the drawing from within inventor, but using vault explorer it is an issue.
We may have to look into the dataset and system to find out more on this issue. Please raise a ticket with Product Support on this so that someone from Support can look into this.
This is an issue our company has also. We commonly find this problem even though we've gone through and checked out all levels including the drawings and made sure all files were up to date before checkign in. Very high on our concern list.
We have this issue as well occasionally with Inventor drawings and assemblies when opening them from the Vault Client. We submitted this as a bug a long time ago and we were told by Autodesk support that opening files from the client is not the preferred method to open Inventor files. When you open the files from Inventor, they always pull in the correct version/revision.
There is definitely something wrong when you get the incorrect child version from the client.
I hope this helps!
Add our company to the growing list... It is happening here as well. Opening a drawing from Vault Explorer is not getting the latest revision.
The suggested workaround is workable, but not acceptable in my opinion. Has Update 1 for 2013 addressed this? We haven't installed that yet.
Scott
I agree with you Scott. It is abolutely unacceptable when a data management tool does not manage your data properly. This is core functionality and must be fixed! I don't understand why this is not a priority.
You should be able to open a file from the Vault explorer and get the right versions just like you do in Inventor. If it does not work and is not the preferred method to open parts, do not allow file open on Inventor files from the Vault client.
This is happening to us as well, in connection with a seperate issue. Details in this thread:
The posts on the second page get into the meat of this topic. I thought I had solved an issue where Version A had been marked released, and people were pulling old versions (which were in vault terms "quick edits" after release). So, I revved to B, and was disappointed to see the same behavior with the new triangle icon. I really thought that was going to work.
Open from Vault, you get one result. Open from Autocad, different results. Unacceptable.
I suspect that BSchubring is correct.
The current behavior for Vault Explorer when double clicking on a file is that is that it gathers up dependent files with the following settings:
I'm guessing that the "Release biased" behavior is what is unexpected for users in this thread. Release biased will cause gathered files to not always be the latest (when there is a released version of a dependent file that is not the latest). There isn't a way to customize what open from Vault Client does.
Workarounds:
I realize that this won't satisfy most on this thread--I just want to explain how it is currently working and what your options currently on. I'm guessing different people with different roles will have different opinions on what the "double-click to open" behavior should be.