Handling Identifier Changes in ReqIF Mapping Files

Overview

This article explains the best practices for preserving attribute identifiers when working with ReqIF mapping files in Data Exchange (DX). It covers common mapping issues and provides solutions for maintaining consistency when exporting and re-importing data.

1. Understanding the Identifier Mapping Issue

✔ Problem: When a customer creates a new export mapping file in DX, new attribute identifiers may be generated, leading to inconsistencies when returning a ReqIF file to a third party.
✔ Cause: If a new mapping file is created instead of reusing the original import mapping file, DX assigns new attribute identifiers, disrupting traceability.

✔ Scenarios Where This Issue Occurs:

1. A customer receives a ReqIF file from a third party.

2. They create an import mapping file in DX.

3. They successfully execute the import into Jama.

4. A new export mapping file is created.

5. The customer executes the export and returns the ReqIF file.

6. The third party may encounter changed attribute identifiers, causing data mismatch issues.

2. Correct Procedure for Preserving Identifiers

There are three viable options to maintain identifier consistency:

✅ Option 1: Reuse the Import Mapping File

• The safest approach is to re-use the import mapping file when performing an export.

• This ensures attribute identifiers remain consistent.

✅ Option 2: Use the "Create New Mapping File" Utility During Import

• When importing a ReqIF file, use the IMPORT create new mapping file utility instead of manually creating a new export mapping file.

• This keeps identifier mappings stable.

✅ Option 3: Manually Edit the Mapping JSON File

• If fields must be added that did not previously exist, manually editing the identifiers in the JSON file is required.

• This approach is necessary if a customer modifies field definitions after the initial import.

3. Best Practices for Avoiding Identifier Changes

🚀 Always reuse the original import mapping file for exports whenever possible.
🚀 If a new mapping file must be created, use the IMPORT create new mapping file utility to prevent identifier mismatches.
🚀 For cases requiring new attributes, manually edit the mapping file JSON to maintain identifier consistency.
🚀 If experiencing issues, review the mapping process before sending the exported ReqIF file back to third parties.

4. Conclusion

✔ Reusing mapping files ensures identifier consistency and prevents issues when exchanging ReqIF data.
✔ Creating a new export mapping file without maintaining identifiers leads to mapping errors.
✔ Manually modifying the mapping JSON is necessary when adding new fields.
✔ Proper mapping practices improve traceability and prevent integration issues between DX and third-party tools.