Certified SOLIDWORKS® Solution Partner|Built for SOLIDWORKS and SOLIDWORKS PDM Professional|Free Community Edition, no key needed

Conversion guides

Convert SLDASM to Parasolid (X_T / X_B) with references

Convert SLDASM to Parasolid X_T or X_B with PDMPublisher: the whole SOLIDWORKS assembly plus every referenced part as its own file, add-in or PDM task.

SOLIDWORKS is built on Parasolid, so X_T is the most faithful copy you can send to NX, Onshape, Solid Edge or any other Parasolid application. PDMPublisher writes the whole assembly as one file, plus one per part and sub-assembly so the receiver can rebuild the structure, in SOLIDWORKS or as a PDM Professional task.

Quick answer

  • Open the assembly, tick Parasolid Text (x_t) under File formats on the PDMPublisher tab, set a filename such as (FileNameWithoutExtension)-(Revision), select Publish.
  • Tick Export references to file formats individually to also get one file per part and sub-assembly.
  • Parasolid Text needs Premium in the add-in (the free Community Edition does PDF, DXF and STEP). The PDM task includes every format.

In SOLIDWORKS: step by step

  1. Open the top-level assembly (in a vault, Get Latest first so references resolve).
  2. On the PDMPublisher tab, select Settings > Publish.
  3. Set Export location and Filename, for example (FileNameWithoutExtension)-(Revision). The .x_t extension is added for you.
  4. Under File formats, tick Parasolid Text (x_t). Tick Parasolid Binary (x_b) too if the receiving system prefers the smaller file.
  5. Leave Export references to file formats individually off for one file of the whole assembly, or tick it for one per part and sub-assembly too.
  6. For every configuration, tick Convert multiple configurations with (ConfigurationName) in the filename; exclude *Flat* in the Configuration Filter.
  7. Select PDMPublisher > Publish, confirm the review dialog, and check Publishing results.

As a PDM task: on every release

PDMPublisher for PDM Professional runs the same engine as a task, so the export happens when the file changes state, not when somebody remembers.

  1. In PDM Administration, right-click Tasks > New Task, choose PDMPublisher, name it and tick the task hosts.
  2. On the Options page set Export Location, for example (VaultRootFolder)\Exports\PARASOLID (no trailing backslash), and the Filename.
  3. Tick Parasolid Text (x_t) under File Formats. 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. For release workflows, enable Get latest revision only, then attach the task to a workflow transition.

Settings that matter

SettingWhat to putWhy
Export references individuallyOn for one file per componentBeside the top-level file; in the task this needs a BOM Template.
Filename(FileNameWithoutExtension)-(Revision)Conveyor-B cannot be confused with Conveyor-C.
Convert multiple configurationsOn, with (ConfigurationName) in the filenameEvery assembly configuration, not just the active one.
Export location(VaultRootFolder)\Exports\PARASOLID, no trailing backslashCreated if missing; you need add and edit permission there.
Export references to file formats individually checkbox in the PDMPublisher Publish settings
Export references to file formats individually writes every referenced part and sub-assembly as its own file.

Naming examples

  • (FileNameWithoutExtension)-(Revision) gives Conveyor-B.x_t.
  • (FileNameWithoutExtension)-(ConfigurationName) gives Conveyor-Short.x_t and Conveyor-Long.x_t.
  • (VaultRootFolder)\Customer Packages\($ProjectNumber)\(TargetExtension) in the task files each format in its own subfolder per project.

If something looks wrong

  • Only the top-level file came out: Export references to file formats individually is off (in the task, the BOM Template is missing).
  • Components are missing: the job needs local copies of every reference. Get Latest first. Suppressed, virtual and excluded-from-BOM components are skipped on purpose.
  • Parasolid Text is missing from the results: the add-in is running as Community Edition. Activate a Premium key under PDMPublisher > License Key, or use the PDM task.
  • Nothing in the folder: you need add and edit permission in the export location. Target a subfolder, not the vault root.

Keep going

Documentation

Frequently asked questions

How do I export a SOLIDWORKS assembly to Parasolid X_T with all its parts?

Tick Parasolid Text under File formats and enable Export references to file formats individually. The assembly and every part come out as their own .x_t in one Publish.

Should I send X_T or X_B?

Parasolid Text (x_t) is the most widely accepted; Binary (x_b) is smaller. PDMPublisher writes both in one job, so tick both if the receiver hasn’t said.

Does the PDM task need anything extra to export the references?

Yes. Pick a BOM Template with name, configuration and quantity columns, then enable Export references to file formats individually. The add-in needs no template.

Is Parasolid available in the free Community Edition?

No. Community Edition does PDF, DXF and STEP only. Parasolid needs Premium in the add-in; the PDM task includes all formats.

Where to next

PDMPublisher for SOLIDWORKS · PDMPublisher for PDM Professional · All features · Conversion guides · Pricing · Documentation · Contact

The SOLIDWORKS add-in is free to start as the Community Edition. The PDM Professional task comes with a 7-day trial. Download the add-in or start the task trial.