Map by lookup list is used when a product, row, or element stores an ID, while the readable name is stored in a separate lookup list in the same source.
Typical example: a product has category_id = 12, and the category list has id = 12, parent_id = 3, name = Chairs. Eofferix can output Chairs or the full path Furniture > Chairs.
Where to Enable It
- Open the settings of the result field, node, or column where the name or path should be written.
- In Additional settings, enable Map by lookup list.
- In tables, the lookup list can be on another sheet. In JSON and XML, choose paths to lookup-list fields inside the source document.
What to Insert
| Mode | Use when | Result |
|---|---|---|
| Lookup value | You need to replace an ID with a name, code, or another lookup field. | 12 becomes Chairs. |
| Section path | You need a section name or a full path built by parent_id. | 12 becomes Furniture > Chairs. |
Settings
| Field | What to select |
|---|---|
| Where the current item ID is stored | The product or row field that stores the ID. If empty, Eofferix uses the current configured field value. |
| Where to take the ID in the lookup list | The lookup-record field compared with the current item ID. |
| Where to take the value / name | The lookup-record field to write into the result. |
| Build full path | Used in Section path mode when the path from parent section to current section is needed. |
| Where to take the parent ID | The parent_id field in the same lookup record. Required only for full path. |
| Path separator | Text between path levels, for example > or /. |
| Multiple value | Enable it if the current field contains several IDs separated by a character. |
Example
| Product | Lookup list | Setting | Result |
|---|---|---|---|
category_id = 12 | id = 12, name = Chairs | Lookup value | Chairs |
category_id = 12 | id = 12, parent_id = 3, name = Chairs; id = 3, name = Furniture | Section path + full path | Furniture > Chairs |
category_ids = 12;15 | Categories with IDs 12 and 15 | Multiple value, separator ; | Chairs;Tables |
If No Match Is Found
If the ID is not found or the lookup list is not fully configured, Eofferix keeps the source value. This prevents data loss when a supplier sends an incomplete lookup list.
Checks
- The current item ID and lookup-list ID must use the same format: for example both
12, not12andcat-12. - ID, parent_id, and name fields must belong to the same lookup record.
- For full path, set the parent ID field.
- For several IDs, enable Multiple value and check the separator.
- This setting is not a consolidated-catalog value dictionary. It reads a lookup list from the source file or table.