Family update

[Dom_CHENTRE]

Hello Alls,
I've got a problem with Creo2.
I have an assembly since a long time that manage several product versions (options).
This is handled with family tables and geometry copies from skeleton parts.
I've made a whole assembly with all instances.
However, all parts are not updated even with "verify in family tables".
Each time I save whole assy, Creo tell me that parts are not updated...
I've send to manufacturing several times wrong parts that has not been updated... 😞
I can't understand why parts are not update.
For some parameters, it's ok.
But for Following skeleton and geometry copy, sometimes not.
I also have Creo 9 (aax...) but not sure this will resolve anything...
Perhaps a problem in my method ?
Thanks for any advice...

[tbraxton]

Map the parent child relationships of each model that is not updating. I would start with the Reference Viewer to determine the external references of each model in question.  Assemblies and skeletons and ECG may create convoluted relations between models. Check the regeneration status to make sure it is green, if not investigate what is not fully regenerated.

In the future, plan the top-down design approach and document how the design intent is defined a propagated to the models. With this documentation, it makes modifications much more efficient.

[Dom_CHENTRE]

Thanks,
But it's already based on Top Down design technique.
- One top assembly

  - A skeleton (3 instances issued from family table)

  - Some sub-assemblies (3 instances issued from family table)

     - part1 (3 instances issued from family table)

     - part2 (3 instances issued from family table)

Big assembly refers on squeleton (***sql.prt)
Then all sub-assemblies and part are supposed to be updated.
But not each time.
I assume My method is to much complex...
Any advice would be welcome 🙂

[tbraxton]

It is difficult to assess what the problem may be without access to the model or very detailed information regarding an example of what is failing. From your above description it seems you have multiple family tables (4x) through the design, and they are dependent on each other when moving down the design structure. I would choose one failed example and map the dependency from the top level to the failed model and then investigate the root cause.