Rules and Restrictions for Copied Replacement Components
Rules for components created using the By Copy option:
You can replace a single part, not a subassembly.
The copy is completely independent; that is, no dependencies back to the replaced model. The operation is analogous to performing a Save As or Copy From operation.
If the part that is copied is declared to a notebook, the newly created part is also declared to the notebook.
If the part that is copied has relations, the new part has relations.
The following models can be copied:
Models with external copy geometry features. The newly created model has the same external references as the original model.
Models that reference assembly features.
All attributes of the part being copied are copied into the new component, including:
All features, including suppressed features.
Colors set at the part level.
Layers, and layer settings and assignments.
Restrictions for components created using the By Copy option:
You cannot replace multiple models.
When you replace a family member (generic or instance) with a new copy, the system does not copy Family Table information from the replaced model.
Rules for copied skeleton models:
A skeleton model can be copied only as a skeleton model, not as a regular part.
A component can become a skeleton model only if it does not violate any accepted skeleton model behavior; for example, it cannot have simplified representations. In addition, the component must be either the first component in the assembly, or the first non-skeleton component in the assembly.
You can copy a part model component into a new skeleton model. You can generate a native skeleton model, based on a native part model, and have it replace the part model in an assembly, with all references remapped to the new skeleton model. This effectively allows a part to be designated as a native skeleton model through the use of a new model file.