Troubleshooting: ID not resolved for CATENTRY table with unique index data error

The error occurs if the input file contains both unique ids and part numbers to resolve the ID.

Problem

The error id not resolved for the table CATENTRY with the unique index data occurs when the input file contains both unique IDs and part numbers to resolve the ID.

Solution

Change your input file so catalog entries are resolved using either all unique IDs or all part numbers. The following examples show how to load product beans and child item beans. The first example produces an error on the second and fourth record; the second and third examples run without errors.

Example of error in input file:
CatalogEntryUniqueId PartNumber ParentPartNumber Type INVQuantityMeasure INVQuantityMultiple TrackingInventory
1100000 XXX_1 ProductBean C62 2 N
1200000 XXX_11 XXX_1 ItemBean C62 2 N
1300000 YYY_2 Product C62 2 N
1400000 YYY_22 YYY_2 Item C62 2 N
Example of correct input file: Load using CatalogEntryUniqueId and ParentCatalogEntryUniqueId to resolve catalog entries. The PartNumber column is ignored when used with unique ids:
CatalogEntryUniqueId PartNumber ParentCatalogEntryUniqueId Type INVQuantityMeasure INVQuantityMultiple TrackingInventory
1100000 XXX_1 ProductBean C62 2 N
1200000 XXX_11 1100000 ItemBean C62 2 N
1300000 YYY_2 Product C62 2 N
1400000 YYY_22 1300000 Item C62 2 N
Example of correct input file: Load using PartNumber and ParentPartNumber to resolve catalog entries:
PartNumber ParentPartNumber Type INVQuantityMeasure INVQuantityMultiple TrackingInventory
XXX_1 ProductBean C62 2 N
XXX_11 XXX_1 ItemBean C62 2 N
YYY_2 Product C62 2 N
YYY_22 YYY_2 Item C62 2 N