Iteration-level relational imports

Use iteration-level relational files to initialize your database from legacy data sources, such as an MRP database or Excel files. These existing iteration records may have been imported in bulk using the ItemMaster.csv file, although they can also be made in the normal course of using PDXpert.

Relational import files add relationships between a parent item's pending iteration and its child items. These relationships are under change control.

Except in the case of file attachments, the import file simply adds a new relationship between existing items; both parent and child items must be in the database. Any number of parent items may be in the import file, and each parent can be related to one or more child items. It's common for some child items to be added to several different parents.

Iteration-level relationships can be added only on a parent item's first pending iteration. After the parent's first pending iteration is released, do not try to import new relationships for that parent item.

Guidelines for importing iteration-level relationships §

Before importing your data, back up your database. The import tool can make major changes to your database, and can overwrite data on previously-imported items. You cannot undo the changes it makes; you can only restore your backup database.

Do not try to add or modify an iteration-level relationship after the parent item's first iteration is released. Only item-level data can be updated after an item's first iteration is released.

If you use Excel as your CSV file editor, it may make undesired changes to values that it interprets as a number. For example, part number strings beginning with zero (e.g., 001234) will often be silently converted to a numeric value (1234). If you have any part numbers, document numbers or other data with leading zeroes, don't use Excel. Instead, use a CSV file editor, Windows Notepad, or other plain text editor (not Word) to edit your import file.

The Batch Importer tool can make an import file .csv template. Select the correct Import Type template, then click the Export button. Most export files contain previously-imported pending data that can be used to confirm that the import is correct.

Import rules §

  • Parent and child items in these import files are matched according to the identification rule specified in Tools ➔ System Rules... Item uniqueness specified by: Number, Organization, Class, Type. Columns not specified by the rule (Class or Type) are ignored during matching.

  • Iterations (revision and lifecycle) are always ignored in the matching (in fact, none of the relational import files include columns for specifying iteration values).

  • Each parent item's list (BOM items, approved sources, references, file attachments) is a complete replacement set. First, the parent item's entire previous list is deleted. Then, the new list is added. If any one row of the parent's set cannot be imported, then the list is not imported.

  • Replacement set members are collected for a parent based on the import file's data. Therefore, the set's parent must be identified consistently in the import file: if you explicitly identify the class or type for one row, the same values must be used for all other rows in that parent's set.

  • The column names in the first row of the import file (the "header" row) must match the definitions in the help topic. The header names are case-sensitive and must be spelled exactly as shown. Every column with data must have a conforming header. Do not include more than one column with the same header name.
  • specified columns may be in any sequence. Extra (undefined) columns in the import file are ignored.
  • Every value must conform to the column's specified type (collection member, string, number, etc.) or be empty. For example, a column that requires a numeric value cannot include non-numeric characters.
  • Leading and trailing spaces are removed from each data element before it's matched or applied. Other space characters are not affected. For example, the value   many  spaces   becomes many  spaces.


Help Guide Contents [as PDF]