Updating Parent assemblies?

[Anonymous]

                We have experienced this issue a few times now, and it is a bit frustrating.  Maybe you can shed some light on this and let us know if there is something else we should be doing. 

Here is the scenario

• Platform assembly was being generated (parent and children), and was released with all the children on 1/7/14.

• One hand rail needed to be changed per the customer request, so it was put into WIP, altered, and released on 1/09/14 as Rev A.

• Vault shows the old version hand rail in the parent assembly thumbnail, even if you open it with “view in window”, so the consumers do not see the current assembly as designed.

• If I open the assembly with Inventor, I get the appropriate view with the Rev A handrail shown.

                We are very nervous that our consumers will be opening out of date views, and be unaware that a detail has changed visually.  If that one handrail is in 50+ assemblies, I wouldn’t expect that we would need to change state and re-release 50+ parent assemblies to get Vault to show the appropriate views.  Our opinion is that if you revise a detail, the assembly should at least update and reflect the detail being changed in the visualization.  Even when I do a manual new visualization by means of a local update, there is no change to what the consumer sees.

Please let me know what can be done to correct this issue.

Thank you,

[JeffPaquette6500]

Once the assembly is checked into Vault, the visualization needs to be updated. The parent needs to be updated to reflect changes made to children. Job processor can be used to update the visualizations after they are checked into Vault. I understand your opinion that Vault should update the parent after child items are updated, however Vault was not designed to do that.

[Anonymous]

Thank You Jeff for your response.

I can see that asking for my wishes would put a large task on the job processor but that's is what it is for.

I can also see that some or most of child revisions would not change the look of the parent drawing. But some most definitely will. In our case the child is a handrail on the parent platform assembly. We change the shape of the handrail and need the parent drawing to show this new change.

Vault does know that the child has changed. (shows it in the Uses Tab with the correct Rev). Vault does know all the assemblies that the child goes into.

How about a option button to update all parents dwf's if a child is bumped to the next revision.

Right now my comsumers can print an assembly drawing and they come to me and ask why that drawing does not match one of hand rails?

Vault 2013 Collaboration FYI.