An SLDASM can open with missing components even when the top-level assembly file itself is valid.
The usual reason is simple: the assembly references separate SLDPRT files or nested SLDASM files that were not included in the handoff or are no longer at the expected relative paths.
A partial assembly can still look plausible, so missing-reference warnings must be treated as a data-completeness problem rather than a cosmetic message.
Why SLDASM files lose parts
Common causes include:
- only the top-level SLDASM was sent;
- referenced SLDPRT files were omitted;
- folders were flattened or renamed;
- duplicate part filenames became ambiguous;
- nested subassemblies were not included;
- files came from different revisions/configurations;
- references point outside the collected project folder.
The correct fix is usually to rebuild the package from the source assembly rather than search randomly for files with matching names.
Start with the missing-reference list
When the viewer reports unresolved components, record the filenames or paths.
That list tells the sender exactly what needs to be supplied.
Avoid replacing a missing component with a different file that happens to share the same name unless revision and source are verified.
A wrong component can remove the warning while making the assembly technically incorrect.
Preserve relative folder structure
Assembly references often depend on paths.
When creating a ZIP, preserve the directory structure used by the source package.
Do not flatten a tree such as:
assembly/root.sldasm parts/housing.sldprt parts/shaft.sldprt subassemblies/motor.sldasm
into one folder unless the source workflow explicitly supports that structure.
Duplicate filenames are especially dangerous after flattening.
Partial assemblies can still produce numbers
Suppose the main housing and motor load but several brackets and fasteners are absent.
The viewer may still return:
- overall dimensions,
- surface area,
- volume,
- mass based on selected density.
Those are properties of loaded geometry only.
Do not report them as complete assembly totals.
Mark the result partial until the missing-reference list is resolved.
Bounding dimensions may hide missing parts
An assembly can have nearly the same outer envelope even when internal components are missing.
That means a plausible X/Y/Z size does not prove completeness.
Use component count, the missing-reference list and expected product structure as stronger checks.
For supplier or quoting workflows, compare one or more known subassemblies or BOM expectations where available.
Rebuild the package from one revision
Mixing files from different revisions can create subtle failures.
A newer top-level assembly may reference a new component name that an older parts folder does not contain. Conversely, an old assembly may load newer geometry that fits but does not belong to that release.
Ask for a collected package produced from one known released configuration.
Keep the revision information with the ZIP.
Convert to STEP only after completeness is understood
STEP can simplify cross-CAD handoff, but conversion does not magically restore missing SLDPRT files.
If you convert a partial assembly, you get a partial neutral file.
Before using the SolidWorks to STEP converter:
- review missing references;
- confirm intended configuration;
- verify units;
- check expected components;
- then convert.
Reopen the STEP and verify the same scope.
If the missing files cannot be obtained
Sometimes the sender no longer has a complete assembly package.
In that case, document exactly what is missing and what the visible model represents.
Do not infer hidden components or approximate total mass as if they were present.
If a STEP export from the original authoring environment is still available, that may provide a complete neutral geometry snapshot even when the native dependency package is difficult to reconstruct.
A practical repair sequence
- Keep the original SLDASM package unchanged.
- Record every missing reference.
- Ask for the referenced SLDPRT/SLDASM files from the same revision.
- Restore relative folders.
- Upload the corrected ZIP.
- Confirm that missing-reference warnings disappear.
- Recheck dimensions and assembly scope.
- Only then use total properties or STEP conversion.
The goal is not to suppress a warning. It is to establish that the geometry being reviewed is the assembly the sender actually intended.
Missing dependencies or an unreadable version?
These need different fixes. Use the source file and the reported result to decide what to request:
| What you received or observed | What to check next |
|---|---|
| Only a root SLDASM file | Request a ZIP with the referenced SLDPRT files and nested assemblies |
| A ZIP loads but reports missing components | Restore the exact dependencies and relative folders from one revision |
| The package contains similarly named parts from several revisions | Ask the sender to collect one intended release; do not guess which part belongs |
| No usable geometry loads from a complete package | Confirm the authoring application and save version, then request a fresh native package or STEP export |
| STEP downloads but still lacks components | Return to the native source package; another conversion cannot reconstruct absent parts |
CADProps supports readable SolidWorks geometry, not every file saved by every release. A failed read is not proof that the file is corrupt. SLDDRW drawings are outside this STEP-conversion workflow.
What to request from the sender
Ask for the top-level SLDASM, all referenced SLDPRT files and nested assemblies, the preserved folder layout, and the intended revision. Ask which application release saved the package and which components should be present. Keep this information with the source; do not put private filenames or project details into a public troubleshooting post.
If the sender can open the complete assembly in the original CAD application, ask them to confirm the selected configuration or product scope before collecting dependencies or exporting STEP.
Upload, convert and verify the repaired package
- Open the corrected ZIP in the SolidWorks viewer. Follow the current upload limit shown in the workspace.
- Check missing-reference warnings, expected component scope and placements. View and measure without an account.
- Register or sign in to use the SolidWorks to STEP converter. Keep the original source package.
- Reopen the derivative in the STEP viewer. Check a known dimension, component scope and critical geometry; review it in the intended receiving CAD/CAM application before release.
Files are uploaded for server-side processing. Uploaded files stay private and temporary files are deleted automatically when they expire; see the supported formats and privacy policy for details.
For a structured final review, use the CAD conversion checklist. A STEP file is a neutral geometry handoff, not a replacement for native feature history or a complete manufacturing definition.
Check a present file before calling it a resolved reference
A dependency can be present in the ZIP yet remain unreadable because its saved version or representation is outside the reader path. Separately record “absent from package,” “ambiguous identity” and “present but unreadable.” Each status asks for a different correction.
After collecting the right dependency, verify its expected placement and geometry rather than only checking that a warning disappeared. Do not substitute a same-named part from another release. The public assembly evidence in opening SLDASM demonstrates a partial result; its envelope cannot validate complete mass, volume or assembly scope.
Original article: CADProps · https://www.cadprops.com/guides/sldasm-missing-parts/