Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

File is not the latest problem

9 REPLIES 9
SOLVED
Reply
Message 1 of 10
AlexFielder
4143 Views, 9 Replies

File is not the latest problem

Hi all,

 

At the suggestion of the @AutodeskHelp twitter account, here is my post on the above error:

 

We are using Vault Pro 2014 Subscription Release 1 Service Pack 1 and have found that when attempting to change the state of some files we are greeted with the following icon/screen in the Change State dialogue:

 

File is not the Latest.png

 

When I mouse-over any of the triangles you can see in the screenshot above, I am greeted with "File is not the latest" - this despite my having just "Got" the latest copy of said file from the Vault.

 

Even though this dialogue is saying that these files don't have a lifecycle definition, they do in fact have one and are all at "Work in Progress" Lifecycle State.

 

Is there an option I am missing which will prevent this from happening in future or is it a bug?

 

Thanks,

 

Alex.

 

9 REPLIES 9
Message 2 of 10

Hi Alex,

 

Please forgive me if I have misunderstood the problem but I think that might be a part of the "Edited Out of Turn" Workflow Improvements introduced in "Autodesk Vault 2014 Subscription Release 1"

 

In the readme for SR1 it mentions the following

 

  • With the current release, when a user requests to download a version of a file that is on the disk already, Vault does not download the file bits. With this release the same workflow is followed. In addition, even for file versions that have been modified on the disk, Vault does not download file bits when a user requests to download the same version of the file. A new option "Force Overwrite" is added in Vault Client's - Get/Check out dialog to allow users to overwrite files which have been modified on disk with or without checking them out of Vault.

So, do you see the same behaviour if you select the Force Overwrite option in the Get / Check Out dialogue box?

 

Get.png

 

 

Let me know if this helps

 

Richard

 

 



If you find my response solves your question, please click the "Accept Solution" below the response

Richard Rankin
Vault Support Specialist
Global Product Support
Autodesk, Inc.

Message 3 of 10
mikel_martin
in reply to: AlexFielder

The change state command in Vault Explorer does not have any corelation to what files have been downloaded to the workspace.

When you select a file for change state, it gathers the children based on the revision of the children the primary file was checked-in with. It never assumes that you wanted newer revisions of the file just because you are changing the state. If the children have been revised out of context and the primary file has not been checked-in while using the newer revision of the files, then the change state command assumes the the primary file is still supposed to use the old revision of the child files.

 

To fix this problem.

Open the primary file (assembly) using latest of all children.

Checkout the primary file.

Check it in.

 

You would need to do this for all sub-assemblies that are currently refferencing historical revisions.

 

Hope this helps.



Mikel Martin
User Experience Architect
Autodesk, Inc.
Message 4 of 10
AlexFielder
in reply to: mikel_martin

Gents, thanks for the responses.

 

Both of which are good answers and I think cover what we're seeing.

 

The "Force Overwrite" option is not something I was aware of, but then I hardly ever expand the check-out dialogue these days - maybe that option could made more prominent?

 

Mikel's fix seems to be what we've been doing to correct this problem (albeit without fully understanding the steps involved or why it worked).

Message 5 of 10
bbuck
in reply to: mikel_martin

Having this issue, and was wondering if you could clarify what constitutes the "primary file"? If you look at Where Used, it can be used in multiple files. So is it the first parent? Or do you need to check out all parents?

Message 6 of 10
ontargetdesigns
in reply to: bbuck

This is all very well if you haven't released your files. Any file within the lifecycle workflow that can be returned to WIP without bumping the primary file revision can be brought into line with the above method.

 

HOWEVER, this is not the case when releasing files.

 

I have found after a number of years of use and extensive research as well as heartache that you cannot prevent the triangles (file is not the latest) from appearing in Vault if the files are being released (locked down) at a designated revision. 

So, although you may Change the State of your drawing with a series of models or attachments at the same time you will still end up with the triangles once the files reach a released state. Why not Release the models first and then drawings afterwards? Answer = why do a job twice when you can do it in one go?

 

Autodesk will tell us to use Quick Change (a side-step to allow spelling mistakes to be put right without bumping the rev) or if you have a very good administrator they will provide you with full access to 'fix' the files. How often will you need to do this your manager asks 'Oh just for everything in vault' is your reply.

 

if you take a look at the following images I think I have spotted where it all goes awry. It's not Vault or Inventor that is the cause of the problem (well that's my belief anyway). The fault Has to be with the Job Processor. How I HATE THE JOB PROCESSOR! Oh how I hate it!

 

Lets think about what Vault and Inventor do, Vault allows data to be stored, renamed, moved, synchronisation of properties and then when Inventor opens the files everything is magically in the right places and understands what Vault has done. Now we enter the twilight zone and change the state of the files and the dreaded JP takes a half-hearted attempt to synchronise these new property updates (WIP is now Checked/Approved/Released) and BAM! the file is not the latest. How on earth did that happen.

 

We use a stepped approach for our lifecycle, we go from WIP to Verification, Verification to Approved and then Approved to Released. Its a fairly long winded lifecycle but everything is fine until the final stages in the JP. Take a look at the images attached and you will see that at an early stage of he lifecycle there is no resave but at Release the JP carries out a RESAVE and then changes the state.VPro1.png

 

 

VPro2.png

 

 

VPro3.png

 

 

VPro4.png

 

Having observed the Job Sever Queue and carried out research via several forums, I have come to the following conclusions:

  1. There are no options to change the priorities of file types or parent / children / attachments scenarios
  2. .dwg files appear to take precedence over other file types even though everything has a priority setting of 100
  3. Only two options available to correct the ‘File is Not the Latest’ issue
    1. Use Quick Change to open and save in order to update with correct revisions
    2. Use full administration rights to open and save in order to update with correct revisions
  4. The Job Processor / Job Queue does not recognise the relationships between attachments, children and parents of files
  5. If Autodesk could find a method in which the Job Processor / Job Queue could recognise the relationships as mentioned in point 4 and manage to process the attachments then children then parents through to a Released state in the Job Queue then the above problem would most likely be resolved

As far as I can tell, this also affects model assemblies and their component children and sub-assemblies but more testing is required to verify this.

 

Unless Autodesk can come up with a viable solution to this problem then the only way to deal with it is to constantly monitor the Vault / Job Processor and resolve the problems as they occur to reduce any waiting time for projects.

 

The Company I am currently contracting for are engaging with Autodesk direct on this issue. The example I have shown above wasn't anything special. The JP had mucked some drawings up during Release so we returned to WIP, renamed them, saveas back to original file name, scanned the hard copies with redpen as pdf. The we attached the old dwg and the scanned pdf. put them all through the lifecycle and 'File is not the latest' spits out at the end.

 

We use 2016 Vault Pro and 2016 Inventor. I had this problem when using 2012, 2013, 2014 software so its not a new problem. Why don't others have the same problem? Could be they don't lock/release their models.

Message 7 of 10
fbk
Advocate
in reply to: ontargetdesigns

This triangle is NOT a problem. It only tells the user that ; You are going to Release (or change state) a file that contains older versions. Maybe that is what the user wants. It is NOT an error, only a massage to the user.

It would be nice if Autodesk gives us an column with version numbers or savedates.

 

Kind regards, Fred Bellekom, Allseas.

Message 8 of 10
dan
Explorer
in reply to: ontargetdesigns

I have the same issue.  It is driving us nuts!  We are currently using Vault Workgroup 2018.  Resolving this is tedious and is causing some of the pre-Vault employees to get frustrated.

Message 9 of 10
dan
Explorer
in reply to: fbk

It is a problem when you are unable to change the state of a drawing, assembly, and child files all at the same time.  It will not allow you to do this in one step.  We have to change the state of the lowest level children and work our way up.

Message 10 of 10
amin.nurdin
in reply to: mikel_martin

it's happening to me until now on version Vault Pro 2021.
and solve by Mikel Martin comments. hopefully can more informative when an error message is shown.
Amin Nurdin
as CAD Administrator
on PT Sanggar Sarana Baja

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report