Resolving "Invalid Document Location" Error in DX Imports

Overview

This article explains why DX may generate an "Invalid document location" error when importing ReqIF files, particularly when Spec Objects lack a Specification, and how to correctly configure the import location.

1. Understanding the Error Message

✔ Common Error Message:

rust

CopyEdit

Invalid document location. Parameter {the Jama item type I'm importing} cannot be under project.

✔ Cause:

• DX requires all imported objects to be within a specification hierarchy (set, folder, or component).

• If Spec Objects are not part of a Specification, DX automatically creates a new set to contain them.

• If the import location is set to an existing set or folder, DX fails to create the new set, leading to this error.

2. Why Is a Specification Still Required in the ReqIF?

✔ DX requires all objects to be part of at least one specification structure.
✔ If objects exist outside of a specification, DX creates a new set.
✔ If the set creation fails (e.g., because the import location is another set or folder), the import fails.

3. How to Fix the Issue

A. Choose a Component or Project as the Import Location

✔ Instead of selecting a set or folder, choose:

• A Component (best option for structured imports).

• A Project (if unsure about hierarchy).

B. Ensure the ReqIF File Includes a Specification Hierarchy

✔ If possible, modify the ReqIF file to include a Specification containing the Spec Objects before import.

C. Allow DX to Create a New Set Automatically

✔ If a specification is missing, DX will create a new set.
✔ Ensure that the selected import location allows new sets to be created.

4. Best Practices to Prevent Import Location Errors

✅ Ensure all Spec Objects belong to a Specification before export from DOORS.
✅ Select a Component or Project as the import location in DX.
✅ Verify that the import location allows new set creation if needed.
✅ Test imports with a small subset before running full imports.

5. Conclusion

• DX requires imported objects to belong to a specification hierarchy.

• Selecting a set or folder as the import location may cause failure if new sets cannot be created.

• Choosing a Component or Project as the import location resolves the issue.