Convert SLDASM to eDrawings (EASM) automatically

Converting SLDASM to eDrawings gives reviewers a lightweight .easm they can open in the free eDrawings viewer, explode, measure, mark up and send back, without a SOLIDWORKS seat. PDMPublisher writes EASM in batch from the add-in, or as a SOLIDWORKS PDM Professional task. The task applies the measurement and file-property preferences on every host, so the file behaves the same for every receiver.

What you get

eDrawings Assembly (easm) is the eDrawings container for an assembly; parts become eprt, drawings edrw. PDMPublisher keeps the valid one per source. With Export references to file formats individually, each part gets an .eprt and each sub-assembly an .easm.

You get one .easm for the assembly, and one per configuration with Convert multiple configurations. The PDM task applies three preferences before saving: allow measurement, save file properties, and save file properties for each component when the output contains assembly components. The export no longer depends on the task host’s stored eDrawings preferences (task version 2026.08.12; the add-in uses the running SOLIDWORKS’ settings).

The manual way, and why it doesn’t scale

Open the top-level assembly, File > Save As, pick eDrawings (*.easm), name it, save. That’s the active configuration only. Repeat for every part you want as its own file, and again for every configuration.

Fine for one machine. For a 200-component release redone at every revision, it’s a day of clicking and a folder that never matches the BOM. Whether the receiver can measure the assembly depends on a checkbox in the Save As dialog that someone forgets half the time.

Convert SLDASM to eDrawings with the add-in

1. Open the top-level assembly in SOLIDWORKS, references resolved (Get Latest first).
2. On the PDMPublisher tab, select Settings, then Publish.
3. Set Export location: a fixed or UNC folder, or placeholders from the >... menu.
4. Set the Filename pattern, such as (FileNameWithoutExtension)-(Revision); the extension is added for you.
5. Under File formats, tick eDrawings Assembly (easm); other ticked formats come out in the same pass.
6. Leave Export references to file formats individually off for one file of the whole assembly, or tick it for a .easm per part and sub-assembly too. No BOM template needed here.
7. Tick Convert multiple configurations with (ConfigurationName) in the filename. The Configuration Filter includes (PROD*) or excludes (*Flat*) by wildcard.
8. Tick eDrawings Part as well when references are exported; PDMPublisher keeps only the format valid for each source.
9. Select PDMPublisher > Publish, confirm the review dialog, and check Publishing results afterwards.

In PDMPublisher for SOLIDWORKS, eDrawings Assembly needs Premium. The free Community Edition does PDF, DXF and STEP only, up to 5 references per run.

Automate it as a PDM task

PDMPublisher for PDM Professional runs the same engine as a task, so the assembly becomes eDrawings on a state change.

1. In PDM Administration, right-click Tasks, select New Task, choose PDMPublisher and name it.
2. On the Options page, set Export Location ((VaultRootFolder)\Exports\eDrawings, no trailing backslash) and Filename; PDM variables such as ($PartNumber) work here.
3. Under File Formats, tick eDrawings Assembly. Keep Export affected document on so the assembly itself is exported.
4. For the components too, set Template to a PDM BOM layout (name, configuration and quantity columns) and enable Export references to file formats individually.
5. Enable Convert multiple configurations and the Configuration Filter as in the add-in.
6. There’s no separate eDrawings checkbox; the task applies the preferences on its own. Update PDMPublisher on every computer that can run the task.
7. Pick Use this version of SOLIDWORKS. For release workflows, enable Get latest revision only; it exports the version tied to the newest revision.
8. Attach the task to a workflow transition, leave it in the right-click menu, or run it from Scheduled Items.

Settings that matter for eDrawings

Setting	What it does	Tip
Export location	Output folder: vault, relative, UNC or outside. Created if missing.	(TopAssemblyFolder)\Exports\(Revision) works; no trailing backslash.
Filename	Static text, placeholders, custom properties or PDM variables.	(ConfigurationName) for configurations, (Revision) for released files.
File formats	Tick eDrawings Assembly (easm). eprt and edrw are for parts and drawings.	Tick all three for mixed documents or references; invalid ones are dropped per file.
Export references to file formats individually	One file per part and sub-assembly, beside the top-level export.	Task: needs a BOM Template with name, configuration and quantity columns.
Convert multiple configurations	Every assembly configuration, not just the active one.	Needs a configuration-specific filename.
eDrawings export settings (task)	Allows measurement and saves file properties, per component too, before writing.	Task version 2026.08.12 or later on every execution host.

Naming and folders

Placeholders resolve when the job starts, so every file is named the same way:

• (FileNameWithoutExtension)-(Revision): Pump-Unit-D.easm in (TopAssemblyFolder)\Review.
• (FileNameWithoutExtension)-(ConfigurationName) with Convert multiple configurations: one EASM per assembly configuration.
• (VaultRootFolder)\Review Packages\($Customer)\(TargetExtension) in the task: easm and eprt folders per customer, from a PDM variable.

Customize Location (Premium in the add-in, standard in the task) gives easm its own folder. eDrawings files usually go to reviewers, so a common setup points easm at a shared review folder while STEP stays in the vault.

Tips and troubleshooting

• eDrawings needs a Premium key, entered under PDMPublisher > License Key. The PDM task is licensed per vault, 7-day trial, every format included.
• Reviewers can’t measure the file? For the task, put PDMPublisher 2026.08.12 or later on every execution host. For the add-in, check the eDrawings options of the running SOLIDWORKS.
• HTML output in the same list needs eDrawings Professional on the computer running the job.
• Missing references? The job needs local copies of every reference. Get Latest first.
• Invalid formats for the source type are dropped; some depend on the SOLIDWORKS version where the job runs.

Availability

Available in PDMPublisher for SOLIDWORKS (the add-in) and PDMPublisher for PDM Professional (the task).

Documentation and related features

• Run a Publish Job (PDMPublisher for SOLIDWORKS)
• eDrawings Export Settings
• SOLIDWORKS assembly documents
• SOLIDWORKS part documents
• SOLIDWORKS drawing documents
• Run as a SOLIDWORKS PDM task
• Convert SLDPRT to eDrawings (EPRT)
• Convert SLDDRW to eDrawings (EDRW)
• Convert SLDASM to 3D PDF

Frequently asked questions

How do I batch export SOLIDWORKS assemblies to eDrawings?

Tick eDrawings Assembly (easm) under File formats, set location and filename, and Publish with the assembly open. A PDM task does the same on a workflow transition.

Why can’t the recipient measure my exported EASM file?

Measurement must be allowed when the file is saved. The PDM task (2026.08.12 and later) enables it automatically; the add-in follows the eDrawings options of the running SOLIDWORKS.

Can I get an eDrawings file for each part of the assembly?

Yes. Tick eDrawings Part too and enable Export references to file formats individually; parts become eprt, sub-assemblies easm.

Can I export every configuration of an assembly to eDrawings?

Yes. Enable Convert multiple configurations and put (ConfigurationName) in the filename.