Family table instance always need verified in ilink?

[btjvesseleng]

We are using wildfire 2.0 and intralnk 3.3. Every time I make a new instance in a family table, the entire table has to be verified. Sometimes when checking in assemblies, intralink says that I need to verify/regenerate the family table of assemblies/parts. If i am not making any changes (like adding a column for a cut in the table) to the table itself shouldn't it just verify just the new instance? Some tables have 50-100 parts and is staring to take up some time. Any comments or helpful tips would be greatly appreciated.

Thanks,

Ben

 

[looslib]

What build of 3.3 are you running. There is a bug in M021 with assembly family tables and it has been replaced by M022.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

 

[Triston]

Build M01 sure seemed to work well... but it ALSO has that instance issue... in fact... once I did the upgrade to it.. Instances that beloged to generics that had been renamed no longer saw the generic!!! The Horror as generics were verified and could not be saved due to the "same name exists"... the instances were all be considered new!!...

The cure, though painful to have to do, was to rename the generic back to it's old name, verify and save it... then rename it back again to its "new" name...