Are You Tracking Imported Geometry in Your SOLIDWORKS Assemblies?
-In real-world projects, assemblies often contain a mix of native and imported components — STEP, IGES, Parasolid, vendor data, legacy files, you name it.
But here’s the question:
How quickly caAre You Tracking Imported Geometry in Your SOLIDWORKS Assemblies?
-In real-world projects, assemblies often contain a mix of native and imported components — STEP, IGES, Parasolid, vendor data, legacy files, you name it.
But here’s the question:
How quickly can you identify which components are imported?
In this video, I’m sharing a practical approach using Advanced Component Selection in SOLIDWORKS. It’s not part of the typical selection workflow — it works through conditional filtering — and it can significantly reduce the time spent manually identifying components.
However, there’s an important limitation:
If an imported file has been further modified using native SOLIDWORKS features, this method may not always flag it as imported. They get identified if those features are deleted (or probably suppressed - haven't tried this)
That opens up a larger discussion around data integrity, design ownership, and model traceability in collaborative environments.
I’m curious —
How do you track imported geometry in large assemblies?
One practical scenario where this becomes critical :
When working on legacy assemblies or customer-supplied data, identifying imported components quickly helps in:
• Deciding rebuild vs. direct edit strategy
• Estimating effort for feature recognition
• Planning design automation workflows
• Avoiding downstream issues in large assemblies
In complex projects, even small visibility improvements can save hours.
If you’ve faced challenges managing imported geometry, I’d love to know how you’re handling it in your workflow and how you identify which components are imported?
In this video, I’m sharing a practical approach using Advanced Component Selection in SOLIDWORKS. It’s not part of the typical selection workflow — it works through conditional filtering — and it can significantly reduce the time spent manually identifying components.
However, there’s an important limitation:
If an imported file has been further modified using native SOLIDWORKS features, this method may not always flag it as imported. They get identified if those features are deleted (or probably suppressed - haven't tried this)
That opens up a larger discussion around data integrity, design ownership, and model traceability in collaborative environments.
I’m curious —
How do you track imported geometry in large assemblies?
One practical scenario where this becomes critical :
When working on legacy assemblies or customer-supplied data, identifying imported components quickly helps in:
• Deciding rebuild vs. direct edit strategy
• Estimating effort for feature recognition
• Planning design automation workflows
• Avoiding downstream issues in large assemblies
In complex projects, even small improvements can save hours.
If you’ve faced challenges managing imported geometry, I’d love to know how you’re handling it in your workflow.