Checkin fails because of verify

[jruffsr]

I have a user that has a family table with two entries. He has verified the entries in the family table tool and then saved the changes. He then tries to check-in the assembly but it fails because the objects are set to unverified. Has anyone seen this behavior before and been able to identify the cause? In previous instances I have been sucessful with changing an attribute on each instance and forcing a save after verify, but in this case that has not worked.
Thanks in advance for any help.
Jeff

 

[Jacoolo]

first - what tool do you use for data managment?
Second - (if PDMLINK) it should be an option Verify and checkin
third - be sure all necessary data is checked out.

I ve seen this many times - people made check-out for entire FT in Pro\E session, being sure everything is ok. But it wasn`t. It appeared that one instance has for example state Approoved, or was checked out by other user

 

[pjw]

Use the option (Intralink 3X):


'Prevent Family Table Instances With Staus':


-Unverified-


-Verfied With Failure-


-Unknown-


Set the tick box to 'Unverified'


Phil

 

[Asho Pulsar]

Make sure all the parts, sub assemblies and main assemblies are verified. After verification u just check and refresh the workspace. If some symbol exists besides of the part name r assy name shows that aome generics has not been verified which are the part of the family table.