Inventor Fails To Pull Latest Children

[cstarker6VCG4]

I included this issue in a more general post, but it was sort of overshadowed by other things and never resolved.

Inventor is not referencing the latest versions of children in assemblies. I see no pattern in what it fails to update.

This problem reared it's ugly head again when an engineer put out a drawing with an obsolete part in a sub-assembly. The engineer checked out the super-assembly, not realizing Inventor failed to update all references, then checked in and accidentally reverted the sub-assembly. This has to stop. How do I get Inventor to never show me these red dots again?

[ihayesjr]

@cstarker6VCG4 

Were the components with the red dots updated after this user pulled the files from Vault?

This will cause the red dots to appear.

For example.

User 1 pulled all the files at 8:00 am and only worked on a drawing or top-level component.

User 2 pulled a sub-assembly at 8:30 am, made changes, and checked them in at 8:45 am.

When User 1 refreshes the list of files at 9:00 am, the sub-assemblies will show in red because they are not the latest version.

[cstarker6VCG4]

They were out of date the instant I opened them so there was no time for another user to edit them.

In your example, User 1's refresh should pull the latest versions so why would they see out of date items in the Vault tree?

[ihayesjr]

@cstarker6VCG4 

When the user clicks the Refresh button, the status of files in the workspace is updated in the Vault Browser; it does not download files.

Also, an Open on a top-level file does not pull down newer versions of files also. 

[cstarker6VCG4]

I feel like I've been here before. Opening a file needs to pull the latest children. Users should not see historic versions unless they specifically set out to do so.

I will experiment with this setting. Deleting the entire local copy of our repository should stop any old versions from persisting on my my local.

[ihayesjr]

@cstarker6VCG4 

Yes, you have been here before.

Solved: Re: Help Configuring Vault To Be Safe - Autodesk Community - Vault

[cstarker6VCG4]

I should have known better. Inventor isn't apply the above setting properly. Random files are left behind. I just opened an assembly that failed to grab latest children which those children were left behind on my local.

How can I get started on an iLogic script that runs for every file on open? The script cannot require "adding to" anything because that requires human input. It needs to be fully automated, of course, otherwise the purpose of protecting the engineer from old data is defeated.

[cstarker6VCG4]

This is still a pervasive issue. Engineers should only see the latest version of children unless they deliberately set out to view older ones. I warned the others that Inventor is not pulling latest versions, but it's so constant that mistakes are still slipping through. Someone recently double-revised an assembly for the same problem because they continuously viewed an older version by accident. Autodesk wasted company time with this bug.

The tooltip has the right idea, local copies should never override the Vault copy unless it's checked out. That's the entire purpose of checking something out. When we check something in, we are telling Vault "ignore my local and use whatever is in the cloud". Why can't the refresh happen automatically on file open?

When can we expect a fix?

I'll open a ticket in the mean time.