Cadshift

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 convert a GeoJSON file to a shapefile and load it into ArcGIS. Your attribute table has changed. The field called municipality_name is now municipali. The field called building_type_code and the field called building_type_category are both now called building_t, except one of them got renamed to building_t0 by GDAL and you missed it. Your spatial join script that references building_type_code now silently returns nulls on every row. This is not a GDAL bug. It is the shapefile format working exactly as designed since 1983. ...

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. ...

The question comes up constantly: you’re in QGIS, you’ve added a vector tile layer from a basemap service or loaded a .mbtiles file, and you want to export those features to a Shapefile or GeoJSON for editing. You right-click the layer and look for “Save Features As” — but the option is either missing or produces empty output. This is not a QGIS bug. It’s a fundamental property of the vector tile format, and understanding it is the difference between a working extraction workflow and hours of confusion. ...

Every SolidWorks API developer has spent hours debugging a macro that produces no error, no exception, and completely wrong output. The SolidWorks COM API is old enough that many of its failure modes predate modern error handling conventions — methods that silently return Nothing, boolean flags that are ignored, and side effects that modify document state without warning. This is a catalogue of the seven most common ones. Each has a pattern, a root cause, and a fix. ...

If your shop uses SolidWorks and your supplier’s shop uses Inventor, at some point you will end up comparing notes on batch DXF export. Both platforms flatten sheet metal and write DXF files. Both can be automated. The workflows look similar from a distance and differ substantially in the details that matter for production pipelines. This is a comparison of the actual automation approaches, not marketing specs. Platform capabilities are drawn from the COM API (SolidWorks) and the ObjectModel/iLogic API (Inventor). ...