Troubleshooting Picklist Mapping Issues in DX Imports

Overview

This article explains how to troubleshoot picklist mapping errors in DX imports, including how to identify the correct picklist and its API ID.

1. Common Cause of Picklist Mapping Issues

✔ Issue: The wrong picklist ID was selected in the mapping configuration.
✔ DX logs only include API picklist IDs, not their labels.
✔ The only way to retrieve picklist labels is via Swagger API or a report.

2. How to Identify the Correct Picklist ID

A. Use the Swagger API to Retrieve Picklist Labels

1. Open Swagger API documentation for your Jama instance.

2. Run the following API call:

   bash

   CopyEdit

   GET /rest/v1/picklists

3. This will return all picklist IDs and their corresponding labels.

4. Cross-check the API ID from the DX log with the correct picklist label.

B. Generate a Picklist Report from Jama UI

1. Navigate to Admin Panel → Picklists.

2. Export a CSV report of all picklists to match API IDs to labels.

3. Compare the imported field’s expected picklist with the actual assigned picklist.

3. How to Fix Incorrect Picklist Mapping in DX

✔ If the wrong picklist ID was selected, update the DX mapping file to point to the correct API picklist ID.
✔ Ensure that the imported data values match the expected picklist options.
✔ If necessary, modify the ReqIF file to align with the correct picklist structure before re-importing.

4. Best Practices to Prevent Picklist Mapping Errors

✅ Before importing, verify picklist mappings via API or Admin Panel.
✅ Use the correct API ID, not just the picklist name, to avoid mismatches.
✅ Ensure that imported values match the expected picklist options.
✅ Test small data imports before running a full ReqIF migration.

5. Conclusion

• DX logs only show API IDs, so picklist labels must be retrieved separately.

• The correct picklist can be identified via Swagger API or a picklist report.

• Updating the DX mapping file with the correct API ID resolves the issue.