Revision files import

This file defines how PDXpert attaches files to document and part records' pending iterations.

Each row in the import file represents an item record with one file that must be imported into the library, and attached to the pending iteration's Revision Files list.

This format is intended to import revision files that are managed under change control.

Do not use this import format for historical or background files; instead, use the item-level file & link import.

This import file is used for creating parent-child relationships only on a pending parent part. Do not reference any parent part that has a released or canceled iteration.

Refer to the help topic How to report, import & export > Import & update items > Iteration-level relational imports.

Do not attach multiple files with the same name to one item revision.

Avoid importing a Windows Link (.lnk) file. The real data file is not saved, and the link file doesn't contain information that's useful to other computers.

The External Data Importer tool can generate a CSV template file, which can be used to import your data. Select List: Revision Files from the dropdown list, click the Export button, and save the file to a convenient location.

Column name Data type Assignment if empty Description
Class string Part or Document Part If not specified, then the parent item's Class is a part.
Owner Organizations home organization Identifies the organization that is primarily responsible for the parent item's specification and which issues the item Number.
Type Document Types or Part Types default member If not specified, then the appropriate type collection is determined by this parent item's Class, and the default member of the resulting type collection is used to match the record's Type selection.
Number string row is skipped REQUIRED: Part or document number. If the value is empty, the row is not imported.
RevisionFile file: length ≤ 1000 characters row is skipped

REQUIRED: This is the full file path and name of the imported file, e.g., C:\MyData\MyFile.txt. The file is attached to the item's Revision Files list. As the file is copied into the system library, its attributes are extracted and used to populate the file's attachment record.

If the file does not exist at the specified path, then the file attachment record won't be created. If the file is one of several files related to an item, none of the files will be attached to that item.

It is highly recommended that the imported files are located on the same physical machine — that is, not on a network or mapped drive — as the importing PDXpert client.


Learn More
Help Guide Contents [PDF]