⚙️ Introduction

This job allows the creation and management of the front-end navigation tree via CSV import.

You can:

Define the navigation structure for your store
Map navigation nodes to one or more classification categories
Organize the display order of navigation categories

⚠️
Important Notes
Full Overwrite: Each new import of navigation categories will overwrite the previous tree. Ensure the file contains the complete navigation structure.
Assortments: It is not possible to associate a custom navigation category with an assortment via Data Hub.

📂 Import model

The CSV file must contain one row per Navigation Category.

📄
Template
You can use the following spreadsheet as a template to structure your import:
Navigations - Template

📋 Fields

Field	Definition	Required for creation	Required for update	Editable	Default Value
`Navigation Category Names`	Display name of the navigation category.	✅	✅	✅
`Navigation Category External Id`	Unique external identifier for the navigation category.	✅	✅
`Navigation Category Parent Id`	External ID of the parent navigation category. Use `Root_default` for top-level nodes.	✅	✅	✅	Root_default
`Classification Category Code`	External ID(s) of the linked classification(s). Use `\|\|` to link multiple classifications.	✅	✅	✅
`Navigation Category Active`	Status of the navigation category.			✅	TRUE
`Navigation Category Position`	Display order of the navigation category (1 to X).			✅
`store`	Store identifier for the navigation. Required in multi-store context. Use `\|\|` to assign to multiple stores.			✅
`CF_customFieldExternalId`	Custom field value. Column name must follow the `CF_camelCaseName` convention.			✅

⚠️
Required Custom Fields
Any custom fields configured as required in DJUST must also be included.

⚠️
Custom Fields — Empty values
An empty Custom Field column in the CSV will delete the existing value in DJUST. Leave the column out entirely if you do not want to modify a custom field.

🧠 Key Business Rules

Overwrite behavior

Each import fully overwrites the existing navigation tree. The CSV file must always contain the complete navigation structure — not just the changes.

Parenting

The Navigation Category Parent Id must reference a category that exists within the same file or already in the system. Otherwise, the node will not be attached correctly.
For top-level categories, use Root_default as the parent ID.

Classification mapping

One navigation node can link to multiple classifications (use || separator).
One classification can only be linked to one navigation node — not more.

Multi-store

Navigation imports are store-specific. In a multi-store environment, ensure the store field is properly set.
Navigation Category External IDs must be unique per store.

Data format

Boolean fields accept TRUE or FALSE (case-insensitive). Any value other than TRUE is interpreted as FALSE.
Navigation Category Position must be a positive integer.

📌
Best Practices
✔️ Always include the full navigation tree in every import file, as the import overwrites the previous structure.
✔️ Validate parent-child relationships before importing — ensure all referenced parent IDs exist in the file or in DJUST.
✔️ Test your import on a staging environment before applying it to production.