topic Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023) in Vault Forum

CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

Steve_Bahr — Wed, 27 Mar 2024 16:04:00 GMT

Greetings.

A user reports that opening an historical version of a top level assembly does not open an historical version of a subassembly within. This behavior is confirmed on my machine.

The workaround:

Ensure all files are checked in.
Delete all local copies from the local workspace (workspace is clean of all files).
From the Vault, do a right-click 'Get' of the target historical version of the subassembly, DO NOT include children.
From the Vault, do a right-click 'Get' of the target historical version of the top level assembly, DO NOT include children.
From Inventor, browse to and open the subassembly from the local workspace, DO allow downloads from the Vault but DO NOT update the subassembly.
From Inventor, browse to and open the top level assembly from the local workspace, DO allow downloads from the Vault but DO NOT update the top level assembly.

This workflow produces the desired results. However, I am looking for a simpler and more elegant way to get there.

Ideas anyone?

Thanks in advance.

Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

ihayesjr — Wed, 27 Mar 2024 18:16:53 GMT

Are you not using "revisions" with Vault Professional?

Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

Steve_Bahr — Wed, 27 Mar 2024 18:31:42 GMT

Yes, we use revisions. Revisions and versions make no difference here.

Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

Steve_Bahr — Wed, 27 Mar 2024 18:34:22 GMT

Yes, we use revisions and lifecycle our production data. Revisions or versions makes no difference here, unless I'm missing something.

Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

ihayesjr — Wed, 27 Mar 2024 18:37:00 GMT

Are you performing the Get from the History tab of the assemblies?

Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

Steve_Bahr — Wed, 27 Mar 2024 19:39:42 GMT

Yes.

Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

ihayesjr — Wed, 27 Mar 2024 20:19:51 GMT

Ok, while you are getting a specific version of the top-level assembly, the Get dialog will always perform the Get using Revision bias.

Let's say an assembly revision\version history looks like this.

Revision A - Versions 1 - 3

Revision B - Versions 4 - 6

Revision C - Versions 7 - 10

The revision\version of the assembly always matched the revision\version of the children to try and make it simple.

You want to get version 5 which is at revision B because you selected version 5 in the History tab, the Get will download the latest version within the revision of the children the assembly used. Therefore, the Get will get version 6 of the child not version 5.

To get version 5 of the child, you will have to get that child before or after getting the assembly by specifically selecting that child version.

Does this represent what you are trying to do?

Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

Steve_Bahr — Tue, 02 Apr 2024 15:14:25 GMT

The user asks if Inventor can pull the subassembly's correct version automatically, per the chosen top-level assembly's version. Right now, the user must do a 'get' on the subassembly's correct version.

Thanks for you help so far.

Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

ihayesjr — Tue, 02 Apr 2024 15:42:48 GMT

@Steve_Bahr

Using my example, are you stating that your user wants to get version 5 of the child because they performed a get on version 5 of the assembly? If so, no. Vault Professional is Revision biased on Gets.

Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

Steve_Bahr — Tue, 02 Apr 2024 15:50:37 GMT

The user wants the version of the child that is associated with whatever
version of its top level assembly. Version or revision makes no
difference, unless I'm missing something.

Re: CANNOT SEE A HISTORICAL VERSION OF A SUBASSY FROM A HISTORICAL VERSION OF ITS TOP LEVEL ASSY (VAULT PRO 2023)

ihayesjr — Tue, 02 Apr 2024 15:52:35 GMT

So if you are asking to pull the correct "revision" of the child that goes with the "revision" of the assembly, Vault already does this.

There is a difference between getting "versions" versus "revisions".