Handling Roundtrip IDs and Conversation Data in DX

Overview

This article explains how roundtrip IDs function in DX ongoing conversations/exchanges, how multiple conversations affect item tracking, and how to share conversation data across users.

1. Problem: What Happens to Roundtrip IDs When an Item Is Part of Multiple Conversations?

✔ Observed Behavior:

• If an item belongs to multiple conversations, it's unclear whether the roundtrip ID field is overwritten.

• If exporting, the same identifier is reused across all conversations.

• If importing, and the ID is different, a duplicate item is created instead of updating the existing item.

✔ Key Considerations:

• ID generation on a new export should be stable (i.e., if the ReqIF file is removed and a new conversation starts, the same ID should be reassigned).

• If the original ID was set via import, it may behave differently.

✔ Workaround (If Needed):

• Use separate fields for each conversation to prevent ID overwrites (but this increases complexity in item administration).

2. Sharing Conversation Data with Other Users

✔ Conversation data is stored as an attachment in Jama.
✔ Any DX user can access it.

✔ Common Misconception:

• Mapping files do NOT contain conversation IDs.

• A conversation ZIP file contains the mapping file and conversation details.

✔ How to Share Conversation Data:

• Provide access to the conversation ZIP file instead of relying on individual mapping files.

• Ensure all relevant DX users have access to the file within Jama.

3. Best Practices for Handling Roundtrip Conversations in DX

✅ Ensure IDs remain stable across exports to prevent duplication.
✅ Use conversation ZIP files (not mapping files) when sharing data with admins.
✅ If necessary, track multiple conversations by using different fields (but avoid excessive complexity).
✅ Before importing, verify that the conversation ID aligns with the intended update.

4. Conclusion

• Roundtrip IDs are reused in all conversations but can create duplicates if different IDs are assigned upon import.

• Conversation data is stored in Jama as an attachment and can be accessed by all DX users.

• Mapping files alone do not store conversation IDs—use the conversation ZIP file instead.