How PDMPublisher (for SOLIDWORKS) seamlessly integrates with SOLIDWORKS PDM Professional

PDMPublisher runs inside SOLIDWORKS and talks directly to SOLIDWORKS PDM Professional through the installed PDM client. The bottom status bar shows a vault selector (e.g., Assemblageddon, Bluebyte), so you can target the exact vault where outputs should be stored. Once selected, everything PDMPublisher follows that vault’s rules.

Vault-aware export location
In Output, the Export Location the blue pill “Vault root folder” is used, then a subfolder \cabinet.

That pill isn’t just text: at runtime it resolves to the actual root of the selected vault, producing a valid vault path. The Evaluated Value line confirms the final, resolved path you’ll get when you publish.

PDM variables in the filename
In Filename, the pills “File name without extension” and “Revision” build a compliant name from PDM context (datacard variables and file metadata). Again, the Evaluated Value shows the exact filename that will be written to the vault.

Accessible, permission-respecting workflow
Because PDMPublisher uses the active PDM session (LoginAuto/SSO), it’s immediately accessible to anyone with a PDM Editor license and a vault view on the workstation. It honors permissions and states: if a variable update or write requires checkout, PDMPublisher checks out, applies changes, exports, and checks in.

Other PDM-aware pills you can use
Beyond Vault root folder, you can compose locations and names with pills like Parent folder, Project, Configuration, PartNumber, Description, Date, and more. PDMPublisher resolves configuration-specific values first, and if a value isn’t found it falls back to the document’s Custom tab.

From the vault picker to the evaluated path/filename previews, PDMPublisher publishes directly into PDM with names and locations driven by your PDM variables. You get repeatable outputs, clean version history, and zero post-publish cleanup.