
Customize Export Location
The Customize Export Dialog panel allows you to specify different output folders for each file format generated during the publishing process. This provides granular control over where different deliverables (e.g., STEP, DXF, PDF) are saved.
Note: This feature is only available in the Premium version of PDMPublisher for SOLIDWORKS and PDM.
Opening the Customize Export Location Dialog
- In the PDMPublisher tab inside SOLIDWORKS, go to the Output section.
- Locate the Export Location field.
- Click the Customize Location button (located to the right of the Browse button).
- The Customize Export Location dialog will open, allowing you to configure per-extension export paths.
How It Works
When enabled, PDMPublisher will override the default export path for any file extension that has a custom location defined. For example, STEP files can be exported to one folder while DXF files are saved elsewhere.
| Extension | Example Custom Export Path |
|---|---|
.pdf | C:\speaker project\pdf |
.dxf | C:\speaker project\dxf |
.step | C:\speaker project\step |
.html | C:\speaker project\html |
.x_t | C:\speaker project\parasolid |
Each file format can be toggled on or off using the checkboxes. When checked, the corresponding location will be used instead of the main export folder.
Saving and Sharing Settings
All export location and output preferences are stored locally in the Windows Registry under the following key:
Computer\HKEY_CURRENT_USER\Software\Blue Byte Systems Inc\PDMPublisher (SOLIDWORKS)
Because the configuration is stored in the registry, it can be exported as a .reg file and shared with other team members. This allows administrators or power users to standardize export settings across the entire design team.
To share settings:
- Open the Registry Editor (
regedit). - Navigate to the key above.
- Right-click the PDMPublisher (SOLIDWORKS) key and select Export.
- Save the
.regfile and distribute it to your team. - Team members can double-click the
.regfile to import the settings into their local registry.
This approach is particularly useful in larger environments where consistent export folder structures and naming conventions are required across multiple users or vaults.