Convert SLDASM to Parasolid (X_T / X_B) with references

Converting SLDASM to Parasolid is the cleanest handoff to NX, Solid Edge, Onshape and the CAM and simulation packages built on the same kernel as SOLIDWORKS. .x_t and .x_b import with no geometry loss. PDMPublisher writes Parasolid Text or Binary for the whole assembly and, with references on, for every part in it, from one job or one SOLIDWORKS PDM Professional task.

What you get

Parasolid comes in two flavors: Parasolid Text (x_t) and Parasolid Binary (x_b). Text is the most widely accepted; Binary is smaller. SOLIDWORKS is built on Parasolid, so this is the most faithful copy you can send to another Parasolid application.

You get one .x_t of the assembly. Export references to file formats individually adds one per part and sub-assembly; Convert multiple configurations adds one per configuration. A receiver rebuilding the structure in NX or Solid Edge usually wants the per-part files. You can tick both variants at once. SOLIDWORKS’ current export options apply.

The manual way, and why it doesn’t scale

Open the top-level assembly, File > Save As, pick Parasolid (*.x_t), 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. A receiver who wants the components as separate files multiplies the count by the BOM length.

Convert SLDASM to Parasolid 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 Parasolid Text (x_t); 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 .x_t 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 Parasolid Binary (x_b) as well if the receiver hasn’t said which variant they want; both come from the same job.
9. Select PDMPublisher > Publish, confirm the review dialog, and check Publishing results afterwards.

In PDMPublisher for SOLIDWORKS, Parasolid Text 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 Parasolid Text 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\Parasolid, no trailing backslash) and Filename; PDM variables such as ($PartNumber) work here.
3. Under File Formats, tick Parasolid Text. 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. Pick Use this version of SOLIDWORKS. For release workflows, enable Get latest revision only; it exports the version tied to the newest revision.
7. Attach the task to a workflow transition, leave it in the right-click menu, or run it from Scheduled Items.

Settings that matter for Parasolid

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 Parasolid Text (x_t), Parasolid Binary (x_b) or both.	Both variants in one job.
Export references to file formats individually	One file per part and sub-assembly, beside the top-level export.	Task: needs a BOM Template.
Template (task)	PDM BOM layout that calculates references, configurations and quantities.	Must include <Name>, <Configuration> and <RefCount>.
Convert multiple configurations	Every assembly configuration, not just the active one.	Needs a configuration-specific filename.

Naming and folders

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

• (FileNameWithoutExtension)-(Revision): Gearbox-C.x_t in (TopAssemblyFolder)\Exports\Parasolid, with each part beside it when references are enabled.
• ($PartNumber)-(ConfigurationName) in the task: PDM part numbers instead of filenames, one file per configuration.
• (VaultRootFolder)\Handover\($Customer)\(TargetExtension): separate x_t and x_b folders under the customer’s folder when both variants are ticked.

Customize Location (Premium in the add-in, standard in the task) gives x_t its own folder. With both variants ticked, give x_t and x_b their own rows so they don’t share a folder.

Tips and troubleshooting

• Parasolid needs a Premium key, entered under PDMPublisher > License Key. The PDM task is licensed per vault, 7-day trial, every format included.
• Missing references? The job needs local copies of every reference. Get Latest first.
• Task missing or wrong references? Check the BOM Template columns. Suppressed, virtual, envelope and excluded-from-BOM components are ignored.
• Exclude *Flat* in the Configuration Filter so flat patterns don’t produce extra model files.
• 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)
• File Formats option
• SOLIDWORKS assembly documents
• SOLIDWORKS part documents
• Extension-specific export locations
• Run as a SOLIDWORKS PDM task
• Convert SLDPRT to Parasolid
• Convert SLDASM to STEP
• Convert SLDASM to IGES

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.