SOLIDWORKS assembly
CAD & 3DSLDASM stores SOLIDWORKS assembly relationships and may reference separate part files. If components are missing, check whether only the assembly was delivered. Collect dependencies and select the intended configuration.
- Main use
- Storing CAD assemblies with referenced parts
- Data type
- Binary data / document
All sections, questions and sources
Content reviewed： · Editor：Kai
Example: a practical checking sequence
Example: an emailed SLDASM has missing parts. Distinguish missing references from suppression/configuration. Request a complete collected package, then compare component counts and placement. Avoid arbitrary renaming during folder organization.
Opening steps
Choose your environment or purpose to see its steps.
Menu labels and support vary by app, OS and version. Preserve the original before making changes.
Troubleshooting by symptom
- Missing parts: SLDASM alone may not include referenced files.
- Hidden components: check configuration, suppression and display state.
- Breakage after renaming: check reference names and paths.
- Limited editing: check loading mode, version and licensing requirements.
- Constraints absent after exchange: neutral formats may not preserve native mates or history.
Transfer complete assemblies or exchange geometry
- Open the intended configuration.
- Collect dependencies with Pack and Go or export suitable exchange geometry.
- Check component counts, configuration, dimensions and placement at the destination.
Exchange geometry is not equivalent to native assembly editing; preserve the assembly and its parts.
Collect references with Pack and Go
Supported collection gathers referenced components and documents; manually choosing visible files may omit nested dependencies.
Source for these steps：Dassault Systèmes · Pack and Go
Missing versus hidden components
Missing files and suppressed components require different fixes; compare warnings with the component tree.
- Ask for the intended configuration.
- Compare references with actual files.
- Use supported CAD management when renaming.
Source for these steps：Dassault Systèmes · Find References
Related-format differences
| Format / purpose | Use and preserved information |
|---|---|
| SLDASM | Assembly relationships and references. |
| SLDPRT | Component part. |
| STEP | Exchange geometry rather than identical constraint editing. |
Handling and security
Inspect collected packages for confidential components and drawings and follow sharing rights.
Questions and answers
Is SLDASM alone sufficient?
Not when components are separate references.
Are invisible components deleted?
They may be suppressed or excluded by configuration.
Can I rename and reorganize freely?
Use supported management to avoid breaking references.
Will a viewer show everything?
It depends on version support and data completeness.
Does STEP preserve native mates?
Identical native editing structure is not guaranteed.
Format facts: name, steward and MIME type
- Formal name
- SOLIDWORKS Assembly
- Steward / specification
- Dassault Systèmes
- MIME type
- Check the producer or implementation; do not assume a single universal MIME value.
Primary and official sources
- Software documentationPack and Go
Collecting assemblies, parts and referenced files
Dassault Systèmes · Link checked： - Software documentationFind References
Checking referenced CAD files
Dassault Systèmes · Link checked： - Software documentationOpening files in eDrawings
Supported formats and assembly viewing
Dassault Systèmes · Link checked：