Resolving "Lookup ID Does Not Belong to Lookup Type" Error in DX Imports

Overview

This article explains how to troubleshoot and resolve the "Lookup ID does not belong to lookup type" error encountered when importing data via DX. This issue typically results from incorrect picklist mappings.

1. Understanding the Error Message

✔ Common Error Messages:

bash

CopyEdit

Lookup id 997 does not belong to lookup type 360 Lookup id 994 does not belong to lookup type 360

✔ Cause: This error occurs when a picklist value (lookup ID) is mapped to the wrong picklist type (lookup type ID).
✔ Example Scenario:

• The Picklist "Category" (ID: 376) contains values:

  • Heading (997)

  • Comment (994)

• However, the import is trying to apply these values to Picklist 360, which is incorrect.

2. How to Identify and Fix Incorrect Picklist Mappings

A. Verify the Correct Picklist and Options

1. Check the lookup type (picklist ID) associated with the field in Jama.

2. Confirm the correct picklist values (lookup IDs) assigned to that picklist.

3. Compare the imported values with the expected picklist options.

B. Use Swagger API to Retrieve Picklist Data

✔ Run the following API call to get picklist details:

bash

CopyEdit

GET /rest/v1/picklists

✔ This will return all picklist IDs and their associated values, helping to cross-check mappings.

C. Update DX Mapping

1. Ensure fields are mapped to the correct picklist type.

2. If needed, remap the picklist values to match the correct lookup type ID.

3. Re-run the import with the corrected mapping.

3. Best Practices for Preventing Picklist Mapping Errors

✅ Always verify picklist mappings before importing data.
✅ Use API tools (e.g., Swagger) to confirm picklist and value IDs.
✅ If importing from another Jama instance, ensure picklists are synchronized.
✅ Document mappings to avoid misalignment in future imports.

4. Conclusion

• This error occurs when picklist values (lookup IDs) do not match the expected picklist type (lookup type ID).

• Using the Jama API or Swagger can help verify picklist mappings before import.

• Ensuring correct field-to-picklist mapping prevents import failures.