Resolving Relationship Mapping Issues in DX After Jama Connect 9.7.0 Update

Overview

This article explains how to resolve relationship mapping issues in Data Exchange (DX) following the Jama Connect 9.7.0 update, which introduced changes to the /relationships API endpoint.

1. Problem: DX Fails to Recognize Relationships After Jama Connect 9.7.0 Update

✔ Error Message in DX Logs:

json

CopyEdit

"Bad Request", "timestamp":"2024-01-23T20:25:01.902+0000", "message":"The lastId parameter is now required to call GET /relationships API endpoint."

✔ Root Cause:

• Jama Connect 9.7.0 changed the relationship API behavior by requiring the "lastId" parameter for fetching relationships.

• Older versions of DX (prior to 3.8.4) used the deprecated "startAt" method for fetching relationships, which no longer works.

✔ Impact on DX:

• DX versions older than 3.8.4 will fail to retrieve relationships because they use the outdated API method.

• Relationship mappings will be empty in exports.

2. Solution: Update DX to 3.9.2 or Newer

✔ Minimum Required DX Version: 3.8.4

• Support for the new relationship fetch method was added in DX 3.8.4.

• If Jama Connect has turned off the "startAt" method, all DX versions before 3.8.4 will break.

✔ Recommended DX Version: 3.9.2

• Ensures full compatibility with the latest Jama Connect API changes.

• Successfully restores relationship mappings in exports.

✔ Steps to Fix the Issue:
1️⃣ Check the DX version you are using (Help → About DX).
2️⃣ If using DX 3.8.3 or older, update to at least 3.8.4.
3️⃣ For best compatibility, update to DX 3.9.2 to ensure full support for relationship mapping.
4️⃣ Re-run the export process and verify that relationships now appear in the mapping.

3. Best Practices for Avoiding Relationship Mapping Issues in DX

✅ Always verify DX compatibility when Jama Connect updates.
✅ Keep DX updated to avoid breaking changes with Jama Connect APIs.
✅ If relationships disappear in mapping, check the DX logs for API call failures.
✅ Use DX 3.9.2 or newer to prevent disruptions in relationship exports.

4. Conclusion

• Jama Connect 9.7.0 changed the API method for fetching relationships, breaking DX versions before 3.8.4.

• Updating to DX 3.9.2 resolves the issue and restores relationship mapping in exports.

• Keeping DX updated ensures compatibility with future Jama Connect API changes.