Skip to main content
17-Peridot
February 11, 2014
Question

Material Assigning in Instances

  • February 11, 2014
  • 4 replies
  • 10541 views

I've added a column for the material in my family table using PTC_MATERIAL_NAME. However, any instance that doesn't use the assigned Generic material has a regeneration issue. Whenever I press regenerate it says "Material XXXX was assigned to the part" in the message log. And this occurs for any higher level assemblies that use this part. I'm expecting no regeneration to occur if nothing has changed. The higher level assy should say "Automatic regeneration of the parts has been completed.". However, with the instance inside of the assembly, it doesn't say that. It keep on regenerating the assembly and saying "Material XXXXX was assigned to the part. Automatic regeneration of the parts has been completed." I would like to avoid this at all costs because I don't like my assemblies to regenerate if nothing has changed. It causes nightmares when the assembly is promoted and released in Windchill but still used in higher level assemblies. Can anyone help me with this? The easy answer would be to not have the PTC_Material_Name in the family table. I would like to avoid that if possible.


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

4 replies

24-Ruby III
February 11, 2014

Joseph,

I tested your problem in Creo Parametric 2.0 M090 (without Windchill). The problem disappeared when I saved Instance Accelerators for family table instances. Unfortunatelly I don't know how Windchill manages Instance Accelerators...

Martin Hanak

jwagh17-PeridotAuthor
17-Peridot
February 11, 2014

Martin,

I did save the instance accelerators for the instances and it still gave me issues when the instances were placed in an assembly. My specific example is a standoff family table where a swage standoff is going in a board assembly.

24-Ruby III
February 11, 2014

Joseph,

it is possible that the problem is related to your data. If you want I can send you my test models (let me know what ProE/Creo release do you use).

Martin Hanak

1-Visitor
February 11, 2014

What problem does it cause?

If the items are released, they can't be checked in, so Windchill won't see any change.

jwagh17-PeridotAuthor
17-Peridot
February 11, 2014

It still regenerates unecessarily, causing any higher level assemblies to regenerate. I'd rather it say "Automatic regeneration of the parts has been completed." if possible. These are going to be library parts for about 30 mechanical engineers. I don't need people complaining that the instance is causing their assemblies to regenerate when nothing changed.

1-Visitor
February 11, 2014

It's probably due to the mass properties being recalculated based on the material properties. I've seen this calculation forced by a relation that sets a parameter equal to the mass properties so that the value of the parameter can be pushed to Intralink or PDMLink.

It's possible that eliminating such a relation might quiet the behavior.

An alternative is to open an SPR with PTC.

jwagh17-PeridotAuthor
17-Peridot
February 11, 2014

Attached is a test assembly (zipped).

Just open it up and press Regenerate. Every time you regenerate it keeps on assigning material to the instance.

10-Marble
February 12, 2014

Does it need to have a material assigned to it? Maybe if you just assign a mass density...

jwagh17-PeridotAuthor
17-Peridot
February 12, 2014

yeah... if there isn't a solution to this, that is what I'll end up doing.

10-Marble
February 14, 2014

BTW, what part is it that it's made in so many different materials that it would need a family table for it? Can't you just make seperate parts?