Skip to main content
Jan 27, 2022 2:55 PM UTC
Acknowledged

Family table option when replacing Extern Copy Geometry source

Related products:Creo Parametric

To improve the top-down design methodology when designing variations based uppon a skeleton that's a family table, we'd like to suggest this improvement.
Youtube unlisted video:

 

This is the setup:

Kristof_D_0-1643294685754.png

A skeleton that contains a family table with the refs for a 3/4/5m machine, those refs are packed in a publish geometry.

Kristof_D_1-1643294738400.png

That Published geometry is taken in with an external copy geometry and used in different features.

Kristof_D_2-1643294773507.png

When saved to a new variant for 3Meter machine.

Kristof_D_3-1643294790903.png

And the skeleton is renamed as well.

Kristof_D_4-1643294806458.png

It's still looking at the original skeleton source for 4 meter.

Kristof_D_5-1643294865068.png

We can do an edit definition and point to the source of the instance of 3 Meter, which has the same feature numbers and ID's.

Kristof_D_6-1643294914221.png

But Creo doesn't treat the family table part as the same or connected, and all features fail:

Kristof_D_7-1643294949463.png

So if there could be an option to replace the source parameter to a family table member, retaining the feature number and ID's, that would save a lot of time rebuilding all the dependent features.

 

Please mind this old idea , showing that it's somewhat possible if the machines would be a family table as well, though mind that a good advice for family tables is that the instances should somehow be 90-95% the same construction. It's no use having 3/4/5 meter variations of assemblies in a family table when they contain a lot of different parts.

Replace External Copy Geometry By Instance - PTC Community

 

Please mind that the demo-files are made in creo 7.0.6

 

4 replies

olivierlp
Community Manager
Jan 27, 2022 3:09 PM UTC

Hello, 

Thank you for your idea and the information provided.

Olivier
olivierlp
Community Manager
Jan 27, 2022 3:12 PM UTC
Status changed to: Acknowledged
Olivier
Apr 29, 2022 8:27 PM UTC

Maybe when using  Rename in session instead of Save as can solve your issue 

Sep 13, 2025 12:05 AM UTC

Family tables instances as a base to derive geometry from seems that it will lead to slow regeneration times, even with the "accelerators" active to acccelerate the retrieval of the instances' geometry.

 

But I do also find the need to have a quick way to change dimensions or activate and deactivate features in a skeleton based on a user configuration. Family tables theoretically should allow this, but if we make a skeleton part as a family table it is not modular, since in the skeleton we might want to reference several groups of geometry that in itself are modular (or standard).

 

Using a regular skeleton where the user will externally reference sub-skeleton parts that might be defined as family tables as suggested, would be an alternative, but in practice does not work.

 

My suggestion if this cannot be implemented as @Kristof_D suggested, is to allow the definition of "local" UDFs inside skeletons, since UDFs can have family table instances, to define common geometry for parts or assembly skeletons that have different standard sizes. Meaning, select a group of consecutive features, right mouse click, and instead of clicking "Group" to make a regular group, add new option "Make Family Table", which will create a local in-place UDF, or special group, where the user can pick dimensions to add for a local family table, like when defining a part family table, or when creating a regular UDF. Here the user would be able to pick dimensions to add, features to supress or unsuppress, (or even parameters to add to the local special group, and use regular pro/program to acess those parameters of the group to activate or deactivate features if needed, like in regular UDFs.).

 

This way inside a single skeleton the user would have access to quickly change a group of dimensions at once, group by group (locak UDF by locak UDF). For groups that might define geometry in the skeleton that appears more than once, or used in other skeletons as well, it could be converted or saved as a reulgar external UDF in an external filename, to be acessible to other users and other skeletons. If this geometry, or local group, is used only once, and in only one skeleton, it would avoid having to create an external regular UDF, to avoid having to manage another external file.

 

In the case of the new "local UDF" group needs to be used more than once in the same skeleton, instead of a copy paste, the user could use a "Copy paste special" where the user would be presented to the option to apply the local UDF at other location in the skeleton, but having the exact same definition of the family table values, defining them only once in the original local UDF, but allowing the user to pick a different instance row in the new location.