Derived configurations allow you to create a parent-child relationship within a configuration. By default, all parameters in the child configuration are linked to the parent configuration. If you change a parameter in the parent configuration, the change automatically propagates to the child.
Consider the following example.
Part1 has three configurations:
- Configurations A and C are top-level configurations.
- Configuration B is a derived configuration of configuration A.
The following table shows the effect on configurations B and C when you
change configuration A.
| Change configuration A and apply
the change to: |
Effect on configuration B |
Effect on configuration C |
| This
Configuration
|
Changes |
Does not change |
| Specify
Configurations (specify configuration A) |
Changes |
Does not change |
| All
Configurations |
Changes |
Changes |
You can override any configurable parameter in the
derived configuration so that the parameter is no longer linked to the parent.
Activate the derived configuration and edit the parameter. The parameter changes in
the derived configuration but not the parent, and the parameter is no longer
linked.
SpeedPak for Large Assemblies
SpeedPak creates a derived configuration of an assembly without
losing references. If you work with very large and complex assemblies, using a
SpeedPak configuration can significantly improve performance. See SpeedPak for details.
Defeature Configurations
You can create a defeatured configuration 
for
assemblies and
parts 
.
For more
information, see Defeature and Defeature for Parts.