CadShift — SolidWorks Automation

The question of SolidWorks versus Fusion 360 for sheet metal comes up constantly in manufacturing communities. Most comparisons focus on modelling speed, K-factor accuracy, or bend table flexibility. What they skip is the output side: what the DXF file actually looks like when it hits the laser cutting operator’s desk, and whether the nesting software can consume it without manual cleanup. This matters because the DXF is the handoff document. Everything downstream — nesting, laser cutting, press brake setup — depends on the geometry, layers, and metadata in that file. A flat pattern that looks identical in both tools can produce dramatically different DXF outputs. ...

You open a SolidWorks drawing, insert a BOM table, and two extra columns appear with headers “hide1” and “hide2”. They contain no data, they don’t correspond to any custom property you’ve defined, and deleting them fixes the problem — until someone inserts a new BOM from the same template and they’re back. This is a BOM template corruption issue, and it’s specific enough that most Google searches for it return outdated forum threads pointing at deleted Dassault knowledge base articles. Here’s what’s actually happening and how to fix it permanently. ...

The same question comes up on every growing engineering team: “We’re using a shared network folder and emailing DWG files. What should we move to?” The answer depends on how many engineers you have, whether you use SolidWorks, and whether your existing team already runs Git for software or firmware. This guide gives you a decision framework by team size, then walks through the actual tradeoffs of each approach. For the technical setup details — Git LFS configuration, PDM Standard installation, file naming schema design — the CAD version control technical reference covers those in depth. This guide focuses on the selection decision. ...

You set up a WithEvents handler in a SolidWorks VBA macro. The macro runs, SolidWorks does something (opens a document, rebuilds, saves), and your handler fires correctly. Then you close the macro editor and try to use SolidWorks normally — the handler no longer fires. The macro is gone, and so is your event subscription. This confuses VBA developers who are used to Office automation, where event handlers in a document’s VBA project persist as long as the document is open. SolidWorks works differently. Here’s why, and how to keep handlers alive when you need them. ...

Engineers searching for “Power Automate convert CAD” are usually trying to solve one of two problems: they have a folder of DWG or STEP files that need to be converted on a schedule, or they want to trigger conversion when a file lands in SharePoint. Power Automate can do both — but the mechanism is different from what most people expect, because there are no native CAD connectors in Power Automate’s connector library. ...

Large assemblies break the assumption that CAD tools “just work.” At some threshold — different for each platform — the software stops being interactive and starts being a waiting exercise. The difference between a team that manages large assemblies well and one that doesn’t is almost entirely about the tools and workflows they choose to use, not about hardware. This guide covers the performance toolkit for SolidWorks, Inventor, and Fusion 360, with specific attention to where each platform’s approach breaks down and what you can do about it before the assembly grows too large to manage. ...

Exporting a hundred drawings to PDF before a design review is one of those tasks that eats an afternoon. With SolidWorks PDM, there are three ways to automate it: the built-in Batch Plot tool, the SolidWorks Task Scheduler, and a custom API script that talks to both PDM and SolidWorks. They’re not equivalent — each has hard limits that determine which one fits your situation. What SolidWorks PDM Batch Plot Actually Does SolidWorks PDM Professional includes a Batch Plot tool accessible from the Windows Explorer PDM client. Right-click a folder or a selection of .slddrw files → Batch Plot. The tool opens SolidWorks in the background (PDM handles the license check), iterates through the selected drawings, and exports them to a configured output path. ...

You export a flat pattern from SolidWorks, send the DXF to the laser cutter, and get a phone call: “There are open loops in your file. The machine can’t run it.” You open the DXF back in SolidWorks, zoom in, and the outline looks fine. Zoom in further. There’s a 0.003 mm gap between two arc endpoints at a spline junction. This problem has two distinct root causes that require different fixes. Conflating them wastes time. Here is what is actually happening in each case. ...

A Reddit post asking about converting solid bodies to individual part files got 77 upvotes. The top comment pointed to Insert → Features → Save Bodies — and multiple replies said they’d never heard of it despite years of SolidWorks use. CSWP holders included. This is not a niche feature. It’s the correct way to extract individual part files from a multi-body part, and it does things that Insert into New Part and manual workflows cannot match. ...

Your machine doesn’t crash. Nothing shows an error dialog. Windows just stalls — File Explorer hangs for 5 to 30 seconds, the taskbar goes unresponsive, and then everything unfreezes as if nothing happened. This happens repeatedly, and it always seems to coincide with working near SolidWorks files. The culprit is sldShellExtServer.exe, the SolidWorks shell extension server, and it’s been causing more friction in SolidWorks 2025 than previous versions. Here’s how to confirm it’s the source and how to fix it without a support ticket. ...