How to Use the SOLIDWORKS ConfigurationManager

The SOLIDWORKS ConfigurationManager lets you manage multiple versions of a part or assembly inside one file. Configurations can control dimensions, suppressed features, components, materials, display states, and other model variations.

What configurations are for

Configurations are useful when several versions of a design share the same basic model. Examples include different lengths, hole patterns, mounting options, simplified versions, left-hand and right-hand versions, or assembly states.

Use configurations when the variations are related and can be controlled cleanly. If versions become too different, separate files may be easier to manage.

Good candidates for configurations share the same design intent. If two versions require different sketches, unrelated features, and different manufacturing notes, they may not belong in the same file.

Create a new configuration

Open the ConfigurationManager tab, right-click the part or assembly name, and add a new configuration. Give it a clear name and description. A useful name is better than a generic label such as Configuration 2.

After creating the configuration, activate it and make the changes that should apply only to that version. Pay attention to whether a dimension or feature change affects all configurations or only the active one.

Check the option being used when changing dimensions or suppression states. Accidentally applying a change to every configuration is one of the most common configuration mistakes.

Control features and dimensions

Configurations can suppress features, change dimensions, and control component states. This is powerful for design families, but it needs discipline. Use design tables or configuration-specific settings when many values need to be controlled.

Always test each configuration after edits. A feature that works in one configuration may fail in another if dimensions, references, or suppressed features change.

For larger design families, a design table can make configuration control more transparent. It also gives you a single place to review dimension values and suppression states.

Use configurations in drawings and assemblies

Drawings and assemblies can reference specific configurations. Confirm that each drawing view uses the intended configuration and that the BOM shows the correct part number, description, and quantity.

In assemblies, check that mates still solve when switching configurations. Suppressed faces, missing components, or changed dimensions can break assembly relationships.

If a configuration is only for fast loading or simplified display, name it that way. This prevents someone from using a simplified configuration in a released drawing by mistake.

Avoid common configuration problems

Configuration problems often come from unclear names, accidental global edits, broken references, or drawing views that point to the wrong version. Keep names consistent and document what each configuration represents.

For production models, check custom properties for each configuration. Part numbers, descriptions, materials, and revision notes may need to be configuration-specific.

Be careful with display states as well. A visual change is not the same as a configuration change, but the two can be used together and may confuse users if names are unclear.

Troubleshooting

If a configuration does not update correctly, rebuild all configurations and check suppressed features. If a drawing shows the wrong geometry, verify the selected configuration for that drawing view. If a BOM is wrong, review configuration properties and component display settings.

Configurations can save a lot of time, but they should stay organized. Use them for related variations, name them clearly, and verify every configuration that will be released or used in an assembly.

When a model becomes difficult to understand, consider whether some configurations should become separate files. A simple file structure is often better than one overloaded master model.

Before releasing a configured model, cycle through every released configuration and rebuild. That quick check catches many suppressed-feature and reference problems before they reach drawings or assemblies.