Extension-Specific Export Locations: One Folder per File Format

One publish job, three audiences: the PDF goes to the released-documents folder in the vault, the DXF goes to the laser cutter’s share, the STEP goes to the supplier portal drop. PDMPublisher’s Locations by file format lets each output format override the main Export location with its own folder, built from the same placeholders such as (VaultRootFolder), (State) or ($ProjectNumber). Together with the Filename pattern and the task’s path options, it gives you full control over where every file lands, in the SOLIDWORKS add-in and the PDM Professional task.

What extension-specific locations do

Every PDMPublisher job has a main Export location: a folder inside the vault, a relative path, a UNC/server path or a folder outside the vault, written as literal text plus placeholders. Locations by file format (documented as Customize Location and shown as Export locations by file format) adds a table with one row per output format. Enable the Use checkbox on a row and type a path, and that format is written there instead of the main location. Formats without an override keep using the main Export location.

The override is per format, not per file. If PDF and STEP are both selected and only the DXF row is enabled, PDFs and STEP files go to the main folder and DXFs, including flat pattern DXFs, go to the DXF folder. The dialog uses the same format names and file-type icons as the File formats selector, so the row you enable matches the format you selected.

Both fields accept the full placeholder set. A DXF override such as \\server\laser\(FileNameNumberRange) and a PDF override such as (VaultRootFolder)\Released PDFs\(State) resolve independently for each file. The evaluated path for every selected format is shown in the add-in’s review dialog before anything is written, and the activity log of the task and the add-in’s Logs tab identify which customized path was used.

Why it matters

Output folders are contracts with other people. The laser operator’s nesting software watches one share. The supplier portal syncs one folder. Quality expects released PDFs in a specific vault tree with workflow permissions. When a single job produces several formats and dumps them into one folder, somebody has to sort them afterwards, and that step is where files get lost, duplicated or delivered stale.

Routing by format inside the job removes the sorting step. It also lets each destination keep its own structure: the vault PDF tree can be organized by state and revision, the laser share by material and number range, the STEP drop flat. Because the paths are evaluated per file from live values, a part that changes project number or state moves to the right folder on the next publish without editing the profile.

For the task, the companion options close the loop in PDM: Create Reference from Destination File to Source File makes the exported PDF traceable back to its drawing in the vault’s reference tree, Delete Duplicates Outside the Destination Folder keeps one canonical copy when a file’s export path changes, and Use @ Tab to Evaluate Paths reads path variables from the @ tab when that is where the card values live.

• Released PDFs into a permission-controlled vault folder, DXFs onto the shop share, STEP files into a supplier drop, in one job.
• Folder trees built from state, revision, project number or numeric part number ranges.
• Traceability from exported deliverables back to source files through PDM references.
• Clean-up of superseded exports when the destination path moves.

How it works, step by step

1. The job starts on the open document (add-in) or on the selected vault files (task). Formats are read from File formats.
2. For each source document and configuration, PDMPublisher resolves the placeholders in Export location and Filename on the processing computer. In the task, Use @ Tab to Evaluate Paths switches variable lookup to the @ tab.
3. For each selected format, PDMPublisher checks Locations by file format. If the row for that format is enabled, its path is resolved and used; otherwise the main Export location applies.
4. Values containing characters Windows does not allow in filenames are cleaned, and the job reports the variable that contained an invalid character. Empty placeholders contribute an empty string.
5. If the destination folder does not exist, PDMPublisher creates it before saving.
6. The exporter writes the file with the extension supplied by the format. If the file already exists in PDM, the task creates a new version; the add-in does the same when publishing through a selected vault context with the required permissions. The check-in comment identifies PDMPublisher.
7. In the task, Create Reference from Destination File to Source File adds a PDM reference from the output to the source, and Delete Duplicates Outside the Destination Folder removes duplicate outputs found outside the destination folder.
8. In the add-in, Open export location on completion opens the main Export location after a successful job; formats written to override folders are elsewhere. Publishing results lists every output with Open folder and Copy path.

Every setting that controls where files go

Labels below follow the add-in’s Publish page; the task’s Options page uses the same names except where noted.

Setting	What it does	Notes / default
Export location	Main destination folder, built from literal text and placeholders. Accepts vault paths, relative paths, UNC/server paths and folders outside the vault.	Created if missing. No trailing backslash. Vault paths need create, check-out, check-in and overwrite permission.
Browse…	Selects a static folder and writes it into Export location.	Use for one fixed folder; use placeholders when the path must vary.
Locations by file format… (Customize Location)	Opens the per-format override table.	Add-in: Premium only. Task: available.
Use (per row)	Enables the override for that format.	Unchecked rows use the main Export location.
Export location (per row)	Override folder for the format; supports the same placeholders.	Each row has its own Browse…. No trailing backslash.
Filename	Output filename pattern; the extension is supplied by the format.	Include (ConfigurationName) when Convert multiple configurations is on, or a sheet name when a drawing yields several files.
File formats	Selects the formats to produce; determines which rows in the override table matter.	Multiple formats per job.
Archive all exported documents (.zip)	Adds the produced files to a ZIP archive.	Use for release or supplier packages. Independent of reference export and merging.
Open export location on completion	Add-in: opens the main Export location after a successful job.	Does not open override folders. Disable for network locations that should not pop up.
Show dialog before processing	Add-in: shows the review dialog with evaluated paths per format.	On by default.
Use @ Tab to Evaluate Paths	Task only: reads variables in Export Location and Filename from the file’s @ tab.	Use when project numbers, customers or release folders are maintained on @.
Create Reference from Destination File to Source File	Task only: creates a PDM reference from the exported file back to its source.	Makes deliverables traceable in the vault.
Delete Duplicates Outside the Destination Folder	Task only: removes duplicate output files outside the destination folder.	Review before use where old deliverables must be retained for audit.
Map Variables Between Source and Destination File	Task only: copies mapped metadata from the source file to the generated output.	Options page, Output section.

Placeholders for paths and filenames

Every path field, the main location, each override row and the Filename, resolves the same placeholder set from the >... menu. The task also exposes vault values such as revision, state, workflow and PDM variables; the add-in exposes SOLIDWORKS custom properties and built-in values from the active document, with PDM values available when a vault is configured under Settings > PDM.

Placeholder	Meaning	Example
(VaultRootFolder)	Local root of the current vault on the processing computer. Preferred way to build a vault path.	C:\PDMVault
(FileFolder)	Folder of the file currently being exported; follows each reference.	C:\PDMVault\Projects\Speaker\Components
(TopAssemblyFolder)	Folder of the top-level file that launched the job; stays fixed while references are processed.	C:\PDMVault\Projects\Speaker
(TopAssemblyName)	Top-level filename without extension.	Speaker
(FileNameWithoutExtension)	Source filename without extension.	Bracket
(FileNameNumberRange)	Fully numeric filename rounded down to a 1,000 range; otherwise the filename.	11000-11999 for 11345.SLDPRT
(FileNameNumberFirst3Digits) … First6Digits	First 3 to 6 digits of the first numeric sequence in the filename.	1234 for PART-123456-A
(FileNameNumberRangeFirst3Digits) … First6Digits	Range built from those leading digits.	1000-1999 for PART-123456-A
(State) / (Revision) / (Version)	PDM workflow state, revision (empty if none) and version.	Released / B / 12
(ConfigurationName)	Configuration being exported; @ becomes At.	Default
(Extension) / (TargetExtension)	Source extension / destination extension. PDMPublisher appends the output extension itself.	slddrw / pdf
(Date), (User), (LaunchingUser)	Processing date, task-host PDM user, launching PDM user.	8-13-2026, TaskHostUser, jsmith
($VariableName)	PDM data card variable for the configuration processed, or from @ with Use @ Tab.	($ProjectNumber) → P-24017

Worked examples. Main location (VaultRootFolder)\Released PDFs\($ProjectNumber)\(FileNameNumberRange)\(State) for 11345.SLDPRT, project P-24017, state Released gives C:\PDMVault\Released PDFs\P-24017\11000-11999\Released. DXF override \\server\laser\(FileNameNumberRangeFirst4Digits) for PART-123456-A.SLDPRT gives \\server\laser\1000-1999. Filename (FileNameWithoutExtension)-(ConfigurationName)-Rev(Revision) gives Bracket-Machined-RevB.pdf and, for the STEP row, Bracket-Machined-RevB.step.

Set it up in the SOLIDWORKS add-in

1. Open PDMPublisher > Settings and select the Publish page. Choose the Publish profile to edit.
2. In Export location, type the main folder or use Browse… for a fixed one. Insert placeholders from the >... menu. Do not end the path with a backslash.
3. Set Filename, for example (FileNameWithoutExtension)-Rev(Revision). Add (ConfigurationName) if you enable Convert multiple configurations.
4. In File formats, select every format the job should produce.
5. Select Locations by file format…. In the dialog, tick Use on each format that needs its own folder, type or browse its path, and select OK. This requires a Premium license; the Community Edition uses the main location for all formats.
6. Optionally enable Archive all exported documents (.zip) and decide whether Open export location on completion should open the main folder afterwards.
7. If the paths use PDM values or (VaultRootFolder), configure the vault under PDMPublisher > Settings > PDM with Use vault.
8. Select OK, then PDMPublisher > Publish. With Show dialog before processing on, the review lists the evaluated folder and filename for every format; the note under Export location reports whether any format uses a custom location. Select Publish.
9. In Publishing results, select an output and use Open folder or Copy path to verify each destination.

Set it up in the PDM Professional task

1. In the SOLIDWORKS PDM Administration tool, open your PDMPublisher task under Tasks or create one with New Task…, select PDMPublisher on the Add-in page and choose the task hosts on Execution Method.
2. On the Options page, set Export Location. Prefer (VaultRootFolder)\... for vault destinations because it resolves to the local vault root on the task computer. Make sure the task user can create, check out, check in and overwrite files there; the vault root itself is usually locked.
3. Set Filename with unique values such as part number, revision, configuration or sheet name.
4. Select the File Formats to produce, then open Customize Location and enable an extension-specific location for each format that needs its own folder, for example DXF to \\server\laser\DXF.
5. Enable Use @ Tab to Evaluate Paths if variables such as ($ProjectNumber) are stored on the @ tab.
6. Enable Create Reference from Destination File to Source File for vault traceability, and consider Delete Duplicates Outside the Destination Folder only after checking that superseded exports need not be retained.
7. Enable Vault Activity Logs with a Log Folder (Vault Only) such as (VaultRootFolder)\Logs\PDMPublisher while testing; the log identifies the customized paths used.
8. Click OK. Attach the task to a workflow transition, run it from the right-click Tasks menu, or schedule it. The Task Details tab lists files checked into the vault with their Found In folder.

Recipes

• Three destinations, one release task. Main location (VaultRootFolder)\Released PDFs\(State); DXF row \\server\laser\DXF; STEP row \\server\suppliers\STEP\($ProjectNumber). Formats PDF, STEP; flat pattern DXF enabled. Create Reference on. Attached to the Released transition.
• Numeric part number tree. Main location (VaultRootFolder)\Exports\(FileNameNumberRange); Filename (FileNameWithoutExtension)-Rev(Revision). Files 11345 and 11901 both land in 11000-11999.
• Project folders from the @ tab. Main location (VaultRootFolder)\Projects\($ProjectNumber)\Deliverables with Use @ Tab to Evaluate Paths on, because ProjectNumber is maintained on @.
• Supplier ZIP. Main location (TopAssemblyFolder)\Exports\(Revision), reference export on, PDF and STEP selected, Archive all exported documents (.zip) on. One archive per assembly revision.

Tips, limits and troubleshooting

• Locations by file format is greyed out in the add-in. It is a Premium feature; the Community Edition writes all formats to the main Export location.
• Files went to the wrong folder. Check which rows have Use enabled; only enabled rows override. The add-in review dialog and Logs tab, and the task activity log, show the evaluated and customized paths.
• Path ends with a backslash. Do not end the export location or any override with a trailing backslash.
• I cannot see the exported files. The destination must be a folder where the publishing user has permission to add and edit files; the vault root is typically locked by administrators. In the task, files saved outside the vault are not tracked in the Task Details tab; use Open Log File.
• Empty folder levels or trailing dashes. An empty Revision or PDM variable contributes an empty string. Use separators carefully so an empty value does not leave an extra folder level.
• Invalid characters. Values with characters Windows does not allow are cleaned before saving and the job reports the offending variable.
• Configurations overwrite each other. With Convert multiple configurations, put (ConfigurationName) in the Filename.
• Open export location opened the wrong folder. It opens the main Export location only; override formats are in their own folders.
• Vault placeholders in the add-in are empty. Enable Use vault under Settings > PDM and select the local vault; PDM-backed values require a local vault view and permissions.
• Duplicates deleted unexpectedly. Delete Duplicates Outside the Destination Folder removes copies outside the destination; review it before using it where release history must be retained.

Availability

Available in PDMPublisher for SOLIDWORKS (the add-in) and PDMPublisher for PDM Professional (the task). Export location, Filename and the extension-specific Locations by file format dialog are shared by the SOLIDWORKS add-in and the PDM Professional task. In the add-in, locations by file format are a Premium feature; the Community Edition uses the single Export location. Task-only companions on the Options page are Use @ Tab to Evaluate Paths, Create Reference from Destination File to Source File and Delete Duplicates Outside the Destination Folder.

Documentation and related features

• Run a Publish Job in the SOLIDWORKS add-in
• Export Location and Extension-Specific Locations
• Sheet metal publishing
• SOLIDWORKS part documents
• SOLIDWORKS assembly documents
• SOLIDWORKS PDM integration
• Conditional assembly processing
• Publishing profiles and company settings
• Run as a SOLIDWORKS PDM task

Frequently asked questions

Can PDMPublisher save PDFs and DXFs to different folders in one job?

Yes. Open Locations by file format (Customize Location in the task), enable the DXF row and give it its own path. PDFs keep using the main Export location.

Do extension-specific locations support placeholders?

Yes. Each row accepts the same placeholders as Export location, such as (VaultRootFolder), (State), (FileNameNumberRange) and PDM variables.

Is Locations by file format available in the free add-in?

No. In PDMPublisher for SOLIDWORKS it is a Premium feature. The Community Edition uses one Export location for all formats. The PDM Professional task includes it.

How do I organize exports by part number range?

Use (FileNameNumberRange) in the path for fully numeric filenames, or (FileNameNumberRangeFirst4Digits) to build a range from the first digits of names like PART-123456-A.

What happens if the export folder does not exist?

PDMPublisher creates it before saving. Inside the vault the user still needs permission to create and check in files there.

How can I trace an exported PDF back to its source drawing in PDM?

In the PDM task, enable Create Reference from Destination File to Source File. The exported file then carries a PDM reference to the model or drawing that produced it.

Why is Open export location on completion not showing my DXFs?

It opens the main Export location only. Formats with an extension-specific override are written to their own folders.