Converting a PDX package for batch import

Last update 2019-02-27

Applies to PDXpert PLM software release 12.0 and later. Earlier PDXpert releases are similar but, depending on the import template, column headers may be different.

PDXpert PLM software batch import process

PDXpert includes a batch import tool that allows you to initialize your new PLM system by importing document and part records, and then attaching files to these records.

If you have a PDX package exported by another system, it can be used as the basis for these item records.

However, PDXpert can't directly read PDX packages—the IPC standard assumes the data flow is PLM to MRP, and the PDX file doesn't include configuration data that PDXpert needs.

Using our free PDXplorer tool, you can view a PDX package and export the package data into CSV files that PDXpert can import. The PDXplorer export files include parts and documents, BOMs, AVL sources (organization records + manufacturer parts), file attachments, and person records. After import into PDXpert, the data can be put under revision control using PDXpert's change workflow.

Setting up PDXplorer §

To configure PDXplorer for exporting your data:

  1. Download and install the PDXplorer tool: https://www.pdxplorer.com/

  2. Replace the standard ExportSpecifications.xml file with specifications for exporting CSV files to PDXpert (you'll need Windows administrator permissions):

    1. In Windows File Explorer, go to the PDXplorer program folder %ProgramFiles%\PDXplorer Viewer\XML\ (for example, C:\Program Files\PDXplorer Viewer\XML\).

    2. Rename the existing standard ExportSpecifications.xml file so you can later identify and restore it: ExportSpecifications-Original.xml

    3. Download and save this file: ExportSpecifications-PDX2PDXpert.xml

    4. Copy the ExportSpecifications-PDX2PDXpert.xml file into the PDXplorer program folder %ProgramFiles%\PDXplorer Viewer\XML\ and rename it as ExportSpecifications.xml

Exporting PDX data to CSV files §

For more detail on using PDXplorer, see the PDXplorer help instructions: https://www.pdxplorer.com/pdxplorer-user-guide.htm#controlButtons

PDXplorer tools

To export your data from the PDX package:

  1. Open the PDXplorer software tool.
  2. Open the PDX package (toolbar button 1).
  3. In the left navigation tree, select the ProductDataeXchangePackage node.
  4. Click on the Export Data... toolbar button (toolbar button 9).

    PDXplorer Toolbar: Export Data

  5. On the Save As window, open the Save as type: dropdown list. The export templates for PDXpert begin with PDX2PDXpert …

  6. Click on the Export Group Files... toolbar button (toolbar button 8).

Reviewing the CSV data before importing to PDXpert §

The IPC-2570 specifiies how to move engineering data to a manufacturing system, not to another PLM system. The PDX file includes a lot of useful data, but should be considered only a starting point for initializing your PLM system.

The PDX package generator tool defines the PDX package content. Some package generators include more information than others, which affects what data you'll need to review, add, modify and delete. The generator tool's documentation may describe what the package contains and guide your review the CSV files.

The IPC-2570 standard is an extensible framework that is not consistently interpreted by package generator tools. Depending on the source software, export templates may need to be changed, and the exported data will probably need some editing.

  • To modify a PDXplorer export template, see: Customizing export formats
  • To review and edit the data that PDXplorer exports, use Unicode-compatible text editors like Notepad++ or specialized CSV editors. Avoid using Microsoft Excel, which can silently reformat numeric and date data, or alter Unicode characters.

Recommendations:

  • Always check the PDX generator tool's version and the package date. The IPC standard allows incompatible export specifications (especially for file attachments), and vendors may change their export specifications over time. Do not assume that PDX packages created at different times or by different PDX generators will share the same format.

  • Check the Persons and Organizations collection import files for completeness.

    • Organizations: Add the DisplayName values. Confirm that PDXpert contains matching Languages, Partner Classifications, Currencies and Countries collection members.

    • Persons: Confirm that PDXpert contains matching Countries collection members. If some persons will have user accounts in PDXpert, you can create their accounts in this file.

  • Review the ItemMaster files:

    • The Class column must show Document for each row that should be imported as a document (part rows can have an empty Class value, or use Part).
    • Each defined set of values must have a matching PDXpert collection member. For example, the values in Owner, Type, Lifecycle, Trustee, DefaultUOM, MakeBuy, CostCurrencyShort and possibly custom attributes must match members of (respectively) Organizations, Part Types or Document Types, Item Lifecycle Phases, Persons, Units of Measure, Currencies and Custom collections.
  • The export files for BOM, sources, file attachments may have rows with empty relationships. Delete all rows where the child data is empty (hint: probably where the ChildNumber or IsFileIn is empty).

  • The PDX package may include documents (as Items). Depending on the data source, the PDX package may show these documents on bills of materials. PDXpert shows the documents separately, on a References list. A copy of the BOM file can be used as the basis for importing documents into items' References lists. Be sure to delete the rows from the BOM import file, if needed.

  • If needed, split the PDX-ListFiles export file into Revision files import and Item files & links import formats. URI links (usually as IsFileIn=No) can be imported into PDXpert's Item Files lists. Rows containing IsFileIn=Yes are usually imported into the items' Revision Files lists.

  • Files exported as a group may include the PDX package identifier, and may need to be renamed. (Search the internet for file renaming tools that can remove extra characters used as PDX internal identifiers.) All file references for importing the physical files must be reviewed for both the correct folder path, as well as the correct file name in the folder.

Importing the CSV files into PDXpert §

Import sequence

Import the files in a sequence that builds on each earlier file:

  1. Organizations collection
  2. Persons collection
  3. ItemMaster
  4. Sources
  5. Bill of Materials
  6. File attachments

Import instructions

For important information on initializing the PDXpert system, see the PDXpert application help topics How to report, import & export > Import & update items >

  • Use the External Data Importer (on line)
  • Organizations collection import (on line)
  • Persons collection import (on line)
  • Item Master import format (on line)
  • Sources import (on line)
  • Bill of materials import (on line)
  • Item files & links import format (on line)
  • Revision files import format (on line)

Final comments §

Limits of this procedure

Pre-release only

This application note is not useful for continuous PLM-to-PLM system transfers.

As noted throughout this topic, PDX packages are not well-suited to move data from one PLM system to another. PDX packages often require additional work before they can be imported into PDXpert. In addition, PDXpert's batch data import tool is used mainly to initialize PDXpert with pending (unreleased) part and document records, and for minor updates to item-level attributes like unit costs and custom attributes. The batch import tool is not capable of importing revised data for released items.

You can, however, export a new BOM revision from a selected item in a PDX package. Import the CSV file into an individual assembly's BOM Markup list using the Import Markup From File ▸ Standard context menu command.

Number of PDX packages

This application note works well for transferring a small number of large product files that were exported at the same time.

If you have many PDX packages, or the PDX packages were exported at different times, then it's more efficient to extract the XML and file attachments directly from the PDX packages. In addition to extracting and merging the data much faster, scripting allows auto-filling missing data, excluding obsolete items, converting unwanted collection members into preferred names, cleaning part descriptions, and detecting systemic data errors.

While the details are too complex for an application note, this is the general procedure:

  1. Disassemble each PDX package as a compressed (.zip) file.

  2. Import the pdx.xml content into database tables.

  3. Rename file attachments from extraction folder using original file names, and map to database records.

  4. Identify data elements that require re-mapping, such as item types, custom attributes, units of measure, contacts, etc. Look for PDX …Other attributes (e.g., globalLifeCyclePhaseCodeOther) that may require adding new members to PDXpert collections.

  5. Reconcile item revisions to identify the most recent. If desired, redirect older revision file attachments to Item Files lists.

  6. Create database queries to generate the CSV import templates for PDXpert.

These steps require scripting skills (e.g., SQL and PowerShell). Contact us if you'd like our assistance.

More information

Before using this application note, review the Import part, document, file data tutorial.

If there's no documentation for the PDX package generator tool, PDXpert's IPC-2570 implementation may be useful.

This application note was relevant to the PDXpert software release that was current at time of publication. Product changes since that time may affect its utility. We'd be happy to assist you in assessing the applicability of this note to your situation.

Learn More
Application Notes
Working within PDXpert
Working with other software applications