Troubleshooting DX Export Issues with Filters & Spec Hierarchy Errors

Overview

This article explains common DX export issues encountered when using filters to export specific sets and requirements. The discussion covers Spec Object errors, deleted/missing items, and DX’s handling of partial hierarchies.

1. Common Export Issue: "Spec Object Not Found" Error

Error Message:

javascript

CopyEdit

Error during EXPORT: SERIALIZATION phase. Spec Object not found, unable to export Spec Hierarchy.

✔ This occurs when DX attempts to export an incomplete hierarchy.
✔ DX requires a complete hierarchy, meaning if a set is exported, all its child elements (folders, requirements) must be included.

Solution:

• Ensure the entire set is included in the export.

• If only a portion of the set is needed, use JCI (Jama Connect Interchange) instead of DX, if available.

• Avoid filtering in a way that excludes parent/child dependencies.

2. DX Export Failing Due to Deleted or Unavailable Items

Error Message:

css

CopyEdit

Response Message: {"meta":{"status":"Not Found", "message":"The item with ID 90129 has been deleted."}}

✔ DX tries to download an item that no longer exists.
✔ This can happen when:

• An item was deleted after the filter was created.

• The filter references an invalid or outdated object ID.

• Permissions restrict access to an item (though this would typically return a 403 error).

Solution:

• Verify that all items in the filter exist and are accessible.

• Update the filter to remove references to deleted or inaccessible items.

• If the item is actually the filter ID itself (as Infineon reported), check for configuration inconsistencies in the export settings.

3. DX Filter Export Limitation: Partial Hierarchy Not Supported

✔ DX does not support exporting partial hierarchies—all children of an exported item must be included.
✔ If a requirement is included in the export, its children must also be exported.
✔ When trying to filter only a Set + Requirements (without a folder), the missing folder structure causes the failure.

Solution:

• Export the entire hierarchy (Set + Folders + Requirements).

• If partial exports are required, use JCI instead of DX.

• Work with Jama Support if a DX workaround is needed.

4. Best Practices for Successful DX Exports

✅ Ensure that all parent-child dependencies are maintained in the filter.
✅ Do not attempt partial exports that exclude required hierarchy elements.
✅ Verify that referenced items exist and are accessible before exporting.
✅ Consider transitioning to JCI if more flexible ReqIF exports are needed.

5. Conclusion

• DX requires a complete hierarchy for exports—partial exports will fail.

• Deleted or missing items can cause errors; filters should be validated before export.

• JCI is the recommended long-term solution for ReqIF migrations.

• If DX errors persist, users should attend a support session with Jama experts for further troubleshooting.