Understanding Attribute ID Mapping in DX & ReqIF Exports

Overview

This article explains how Jama Connect’s Data Exchange (DX) handles attribute ID mapping when exporting data in ReqIF format, common issues with incorrect IDs, and best practices for verification and reimporting.

1. How DX Maps Attribute IDs in ReqIF

✔ DX assigns Jama API IDs to ReqIF IDENTIFIERS during export.
✔ This mapping is stored in the mapping file (JSON format) for reference.
✔ ReqIF tools should preserve these Identifiers when re-importing data. However, some tools do not, leading to mismatches.

2. Common Issues & Troubleshooting

A. Incorrect IDs in Exported ReqIF Files

✔ Issue: Some customers noticed different IDENTIFIERS in ReqIF exports, even when the correct IDs were originally used.
✔ Cause: This can happen due to configuration mismatches, missing conversation mode, or different profile settings in the importing tool.
✔ Solution:

• Use ReqIF Studio to inspect ReqIF XML structures and verify ID integrity.

• Ensure mapping files are correctly configured in JSON format.

• Compare IDs between exports to pinpoint where the discrepancy occurs.

B. Losing ID Consistency on Re-Import

✔ Issue: When re-importing data, some tools fail to maintain the original attribute IDs.
✔ Cause:

• The import tool is not using conversation mode, causing it to treat each import as a new entity.

• Different ReqIF processing profiles may alter or regenerate IDs.
  ✔ Solution:

• Enable conversation mode to maintain consistent identifiers across imports.

• If conversation mode isn’t an option, generate a new mapping file for each export/import cycle.

3. Best Practices for Ensuring Correct ID Mapping

✅ Verify attribute IDs in the ReqIF file using ReqIF Studio before and after export.
✅ Ensure mapping files (JSON) store correct identifiers and are referenced properly during re-import.
✅ Use conversation mode when reimporting data to preserve original attribute IDs.
✅ Document ID transformations across exports to track inconsistencies over time.

4. Conclusion

DX maps Jama API IDs to ReqIF IDENTIFIERS, but maintaining correct ID mappings requires proper configuration and import settings. Enabling conversation mode is the best way to ensure ID consistency, while tools like ReqIF Studio help troubleshoot mismatches.