Article - CS128366
  4 Votes

Incompatibility in Family Tables between Generic and Instance causes Problems by Revise and Checkout in Windchill

Modified: 25-Mar-2020   

Applies To

  • Creo Parametric 1.0 to 4.0
  • Pro/ENGINEER and Creo Elements/Pro Wildfire to Wildfire 5.0
  • Windchill PDMLink 6.2 to 11.0
  • Windchill ProjectLink 6.2 to 11.0
  • Pro/INTRALINK 8.x + 6.2 to 11.0
  • Windchill PDM Essentials 6.2 to 11.0
  • PTC Arbortext Content Manager 6.2 to 11.0


  • Under certain circumstances, it is possible to create an incompatibility in Windchill with regards to family tables:
    • The latest version of a generic model references to an earlier or non-latest version of an instance
    • The latest version of the same instance references an earlier or non-latest version of the generic
    • Not all latest revisions of instances refer to the same non-latest generic
  • When such a configuration exists, it can prevent certain actions and cause unexpected behavior:
    • It is not possible to revise the whole family table
    • It is not possible to check out the entire family table
    • Add to workspace of a family table shows some members out of date even though the latest configuration was selected
  • The issue can be reproduced by the following workflow:
    • ​Create two workspaces, WS1 and WS2
    • Create table structure with generic: gen.prt(A.1) instances: inst_1.prt(A.1), inst_2.prt (A.1)
    • Add the FT structure created above to both workspaces
    • In WS1 revise inst_1.prt(A.1). As a result that workspace will contain the family table structure: generic: gen.prt(A.1) instances: inst_1.prt(B.1), inst_2.prt (A.1)
    • In WS2 checkout and then check in entire FT structure (generic gen.prt(A.1) instances: inst_1.prt(A.1), inst_2.prt (A.1). As a result that workspace will contain the FT structure: generic: gen.prt(A.2) instances: inst_1.prt(A.2), inst_2.prt (A.2)
  • When a mismatch of revisions or versions occur, how to bring all members of a family into the latest revision?
  • Not able to delete the latest iteration of a generic item that seems corrupted
This is a PDF version of Article CS128366 and may be out of date. For the latest version click