SwMacroFlow
.swp macro
Save eDrawings: share files without SOLIDWORKS
Exports the open document as an eDrawings file, for sending to people who do not have SOLIDWORKS.
Download Save eDrawings.swp Get SwMacroFlow
Put the downloaded file in this folder, then open SwMacroFlow and choose it from the library.
%LOCALAPPDATA%\SwMacroFlow\macrosRuns per file — point the scope at a folder and it exports every document in turn.
Inputs
| Field | Purpose |
|---|---|
| OutputFolder | Where the file goes. Blank saves it beside the document. Created if missing. |
| OutputName | File name without an extension. Blank uses the document's own name. {Property} placeholders work. |
| Overwrite | On by default. Clear it to skip documents whose eDrawings file already exists. |
The extension follows the document
| Document | Written as |
|---|---|
| Part | .eprt |
| Assembly | .easm |
| Drawing | .edrw |
There is no format field, which is the point: a mixed folder of parts, assemblies and drawings exports in one pass without anyone choosing per file. An extension typed into OutputName is stripped rather than honoured, so naming a part export assembly.easm cannot produce a file SOLIDWORKS refuses to write.
Results
Reports the path it wrote, or decodes the SOLIDWORKS error:
| Reported as | Cause |
|---|---|
| The installed eDrawings version cannot write this file | eDrawings older than the document |
| eDrawings export is not available in the current SOLIDWORKS licence | Translator not installed or not licensed |
| The target file is read-only | The existing eDrawings file is read-only or checked in |
| The file is locked by another program | Something else has the output open |
Chaining
Safe anywhere in a chain. It does not save, rebuild or close the document.
Pair it with Set Custom Property earlier in the chain to stamp a revision before publishing, and the exported file carries the new value.