Convert SLDPRT to Parasolid (X_T / X_B) in batch

Converting SLDPRT to Parasolid is the cleanest handoff to any Parasolid-based system. NX, Solid Edge, Onshape, many CAM and simulation packages and SOLIDWORKS itself share the kernel, so .x_t and .x_b files import with no geometry loss. PDMPublisher writes Parasolid Text or Binary for every part, configuration and body in one batch, or as a SOLIDWORKS PDM Professional task.

What you get

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

You get one .x_t (or .x_b) per part, per configuration with Convert multiple configurations, and per body with Split bodies (body name appended). Tick both variants if the customer hasn’t said which they prefer. SOLIDWORKS’ current Parasolid export options apply.

The manual way, and why it doesn’t scale

Open the part, go to File > Save As, pick Parasolid (*.x_t), set folder and name, save. Repeat for every configuration, and again for every body you want as its own file.

Fine for one part. For forty, or a supplier package redone at every revision, it’s an afternoon of clicking and badly named files. Multi-body weldments and tooling inserts add another loop: one body per file, by hand.

Convert SLDPRT to Parasolid with the add-in

1. Open the part in SOLIDWORKS, saved, references resolved. An assembly works too if you want its parts.
2. On the PDMPublisher tab, select Settings, then Publish.
3. Set Export location: a fixed folder, UNC path, relative folder, or placeholders from the >... menu.
4. Set the Filename pattern, such as (FileNameWithoutExtension)-(Revision); the .x_t extension is added for you.
5. Under File formats, tick Parasolid Text (x_t). Other ticked formats come out in the same pass.
6. Tick Convert multiple configurations and put (ConfigurationName) in the filename so configurations don’t overwrite each other. The Configuration Filter includes (PROD*) or excludes (*Flat*) by wildcard.
7. Tick Split bodies for one file per body, body name appended.
8. Tick Parasolid Binary (x_b) too if the receiving system prefers it.
9. Select PDMPublisher > Publish; the arrow beside it runs a named profile at once. Confirm the review dialog if it appears.
10. Open Publishing results to see every file, its configuration and destination.

In PDMPublisher for SOLIDWORKS, Parasolid Text output needs Premium. The free Community Edition publishes 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 parts become Parasolid Text when they change state.

1. In PDM Administration, right-click Tasks, select New Task, choose PDMPublisher and name it; users see that name in the right-click menu.
2. On the Options page, set Export Location and Filename. (VaultRootFolder)\Exports\ParasolidText keeps output in the vault, a UNC path keeps it outside; no trailing backslash.
3. Under File Formats, tick Parasolid Text (x_t).
4. Enable Convert multiple configurations and the Configuration Filter as in the add-in, with (ConfigurationName) in the filename.
5. Enable Split bodies for multi-body parts.
6. Tick Parasolid Binary (x_b) as well when the downstream system needs it.
7. Pick Use this version of SOLIDWORKS: an installed year on the host, or Latest. For release workflows, enable Get latest revision only too; it exports the revised version, not work in progress.
8. Attach the task to a workflow transition, leave it in the right-click menu, or run it from Scheduled Items.

A task run on an assembly needs Template set to a PDM BOM layout with name, configuration and quantity columns, and Export references to file formats individually enabled. A single part needs neither.

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) and/or Parasolid Binary (x_b).	Both variants can be ticked; invalid formats are dropped.
Convert multiple configurations	Every configuration, not just the active one.	Needs a configuration-specific filename.
Configuration Filter	Include or exclude by name or wildcard.	Exclude *Flat* to skip flat patterns.
Split bodies	One file per body, name appended.	Flat pattern DXF has its own per-body option.
Customize Location	Per-format folders overriding the main one.	Premium in the add-in.
Use this version of SOLIDWORKS (task)	Which installed SOLIDWORKS year runs the export.	That version’s export options apply.

Naming and folders

Placeholders resolve when the job starts, so one profile or task names every Parasolid the same way:

• (FileNameWithoutExtension)-(Revision): Insert-A.x_t in (TopAssemblyFolder)\Exports\Parasolid.
• (FileNameWithoutExtension)-(ConfigurationName) with Convert multiple configurations: one Parasolid per size of a configured part.
• (VaultRootFolder)\CAM\(FileNameNumberRange) in the task: files grouped into numeric ranges from the first digits of the part number.

Customize Location (Premium in the add-in, standard in the task) gives each format its own folder: enable the x_t row to override the main location for Parasolid only. Give x_t and x_b separate rows when both are ticked so text and binary don’t land together.

Tips and troubleshooting

• Activate a Premium key under PDMPublisher > License Key; the PDM task is licensed per vault and includes every format.
• Some formats depend on the SOLIDWORKS version installed; if one vanishes from the results, check what’s installed where the job ran.
• For weldments and multi-body tooling, Split bodies gives one Parasolid per body. Rename bodies in the FeatureManager first so the output names mean something.
• Can’t see the exported files? You need add and edit permission in the export location. The vault root is usually locked; target a subfolder such as (VaultRootFolder)\Exports.
• Save and Clear Logs packages the session log for a support request.

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 part documents
• SOLIDWORKS assembly documents
• Extension-specific export locations
• Run as a SOLIDWORKS PDM task
• Convert SLDPRT to STEP
• Convert SLDPRT to ACIS (SAT)
• Convert SLDASM to Parasolid

Frequently asked questions

What is the difference between X_T and X_B when exporting from SOLIDWORKS?

X_T is Parasolid Text, X_B is Parasolid Binary. Same geometry; text is more widely accepted, binary is smaller, and PDMPublisher can write both in one job.

Can I convert every configuration of a part to Parasolid in one go?

Yes. Enable Convert multiple configurations and put (ConfigurationName) in the filename.

How do I get one Parasolid file per body of a multi-body part?

Tick Split bodies. Each body goes to its own file with the body name appended.

Can PDM Professional export Parasolid automatically on release?

Yes. A PDMPublisher task with x_t or x_b ticked can run on a workflow transition, from the right-click menu or on a schedule.