Importing duplicate records

You can import duplicate records when you import all of your records. Consider these requirements:

• Imported duplicate records must have a pointer to their original ID.
• You must indicate which field in your import schema maps to the original record ID. The original record is used to locate the parent of the duplicate record. Import the parent record before importing child records.
• Within the Rational® ClearQuest® environment, duplicate records are handled by using a Duplicate state and action. Verify that your import schema includes both.
• The import schema must also include the state of the record before it was changed to the Duplicate state.

If you used the Export wizard to export data from another Rational ClearQuest database, a separate import file for duplicate records is created.

Another method for importing duplicate records is to create a separate import file for these records, as you do for history and attachments. You can then import all other records (excluding the child records) and import the duplicates later.

When importing records separately, in the Import wizard - Select a record type window, click Yes to update existing records.