Handling Tables in DOORS 9.6 and Data Exchange (DX)

Overview

This article explains how DOORS 9.6 handles tables in ReqIF exports, how Jama interprets them, and best practices for ensuring proper name mapping in Data Exchange (DX).

1. How Does DOORS 9.6 Handle Tables?

✔ Tables in DOORS can be formatted in two ways:

• OLE Objects: Tables are embedded as images and imported into Jama as non-editable graphics.

• Built-in DOORS Tables: Each table is structured as individual requirements, with relationships between cells.

✔ Issues When Importing DOORS Tables into Jama:

• Table data may break into separate requirements, losing original formatting.

• Some tables may display "undefined" in the name field due to differences in how DOORS and Jama handle name attributes.

• DOORS dynamically assigns names based on whether the object is a folder, requirement, or reference.

2. How to Fix "Undefined" Names in Jama After Importing from DOORS?

✔ Mapping ReqIF Attributes in DX:

• Map ReqIF.ChapterName and ReqIF.Text to the Jama name field.

• The first attribute with data will populate the name.

• If both attributes contain data, the last one mapped will take precedence.

✔ Alternative Fix: Using Document Key for Name Handling in DX

• Navigate to File → Settings in DX.

• Enable the option to use Document Key (Global ID) when name is undefined.

3. Best Practices for Handling Tables in ReqIF Exports

✅ If tables are meant to be static, use OLE objects.

• This ensures tables appear correctly in Jama but are not editable.

✅ If table relationships matter, verify name mapping settings in DX.

• Use ReqIF.ChapterName and ReqIF.Text mappings to prevent undefined names.

• Test imports before finalizing mappings.

✅ Avoid using DOORS tables in round-trip ReqIF exchanges.

• Round trips may break relationships between table cells or incorrectly structure data.

4. Conclusion

• DOORS tables can either be embedded as OLE objects (static images) or structured as individual requirements.

• DX users must correctly map ReqIF attributes to prevent "undefined" names in Jama.

• For best results, OLE objects should be used when table formatting is critical.