More fun with Family Tables

[msexton]

I'm finding a large number of family tables that have not been handled properly when adding new instances to the FT or making other changes to the generic

The assemblies that have instances assembled before the unfortunate handling seem to be stuck in time with the version of the generic just before mishandling. Assemblies having an instance assembled after the mishandling seem to be doing fine with updating.

But before and after assemblies cannot be brought into the same workspace. As an example Windchill returns and error like version 3.8 already exists in workspace, overriding this conflict would overwrite the existing version with different version 2.6.

I only know of 2 ways to correct this. 1 would be to remove the family table instances from the assembly, that is pulling the older version, then add the instances back to the assembly from the latest version of the FT. The 2^nd would be to break the FT apart into individual stand alone parts.

Both of these seem to be unacceptable to management here if there is any other way to correct the issue.

Does anyone know of another method of correcting this?

Marshall Sexton
Master Modeler

NABI USA

[mdavis-2]

This occurs when an instance is rolled to a higher revision and then set back to a lower revision. The conflict occurs when an assembly contains 2 or more instances from the same generic, one of which has been revisioned up and then back.
If you don't mind all instances advancing one revision level, export the generic from Windchill and then reimport at the next revision level.
-Marvin