
The first type is the Generic, which is the “parent” of the table and contains the modifiable parameters in a spreadsheet. Creo Family Tables consists of two different part types. Family Tables are analogous to NX Part Families. The other functionality that we are going to discuss in this article is the migration of Creo Family Tables. Finally, if associativity is desired between the source and target parts, CMM needs to bet set to Feature migration mode. Another point is that the ECG feature should be up-to-date in Creo and regenerate correctly prior to migration.

If this scenario happens it is quite simple to repair the un-associative feature using the standard part repair workflow discussed in an earlier article. The Data Access Feature that accompanies the Body will contain the source part information, but no link can be established. If the target part is migrated alone then the Copy Geometry feature becomes a B-Rep Body feature. The first item is that both the source and target parts need to be migrated in the same migration run to preserve the associative link between the two. Consequently it makes sense that during migration External Copy Geometry features are converted to Linked Bodies. There are a few items that the user needs to be aware of when migrating parts with ECG’s. The External Copy Geometry command is very similar to NX’s WAVE Geometry Link command. We will focus on two Creo functionalities, External Copy Geometry, and Family Tables. Today’s article will focus specifically on migrating Pro/Engineer and Creo data. Welcome to another edition of our Migration Mondays blog.
