cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Regenerate renamed features in TopDown approach with family tables.

Regenerate renamed features in TopDown approach with family tables.

When applying the topdown approach for machine design and their variations, it's often the case that it starts like this.

  1. A general skeleton is made
  2. Different datum features/coordinate systems are made to indicate the position of seperate modules.
  3. A Family table is made that has different values for the position of those modules (f.e. larger machines have some components further from eachother).

If you were to rename a datum feature (point or csys) in the main skeleton and you want this name to be updated in the instances, a normal regenerate won't work, it has to be done by an edit definition.

In order to avoid forgetting or overlooking some instances we'd like to see creo improved so the renamed features get their name updated by the regenerate action.

1 Comment
S_Edgenear
14-Alexandrite

In the inheritance feature it happens the same. If we rename datum planes, coordsys, or points on the original part, after regeneration, the derived component looses the renamed datum names, getting back to system defined ones. It would be nice to improve this as well, and also add a context menu command when clicking a renamed feature in the model tree to explicitly delete the user name, and get back to a default / system named one. This is because if we accidently rename the wrong feature, we cannot back to the original name.