You can have some special Custom Fields that have a hierarchical structure - known as the Hierarchy Custom Fields.
This means that you have Custom Fields that are dependent on each other.
But before you can start using it - you need to "build" the hierarchy here in Admin. This means that you have to define each level in the Hierarchy and set which Allowed values there can be for each level.
Let's say that you build two levels: Level1 and Level2. The Level 2 dropdown content on the Style page depends on what the user has selected on the Level1 dropdown.
This will be a tree structure - much like this one.
- Setup Hierarchy
- Edit the Setup
- Delete a Hierarchy Custom Field
- Import Hierarchy
- Use the values on the Style level
On Admin-Custom Fields click on "Add Custom Field"
On the pop-up, you select the option "Hierarchy Values"
You have to start with creating the first level.
This means that this level can NOT have any mother level. So you do not enter anything on the first screen in the pop-up.
Just click on Next
The next step is to name the level and set all other needed options - these are just the same as for any other Custom Field.
You do have to select if you will sort your Hierarchy values by ID or Value - this is done by selecting the needed radio button.
Decide if the Hierarchy Custom Field is needed in the Thumbnail Print "Group by"
Click on Next.
Now it is time to add the Allowed Values for your First Mother Level (These are the values the user will see in the dropdown on the style page.)
It is important to notice that it is possible to create more than one top-level (a Hierarchy Custom Field that does not have a Mother Level). If you do that - you will have several independent hierarchies.
Now it is time to create the next level in your hierarchy. Again you click on "Add Custom Field" and select "Hierarchy Values"
Now you must select a Mother Level.
Once you have done that you click on Next:
In the next step, you can name the Custom Field and set whatever options you need for it.
Once done - you click on Next.
In the next pop-up, you have to select which of the Mother level's Allowed Values you want to create the next-level Allowed Values for - now you are building the tree structure. In this example, you have to select one of the allowed values that were created in Level1 (Mother Level).
You have selected Dress and now you need to add the Allowed values:
Here you can click on:
- Previous - will send you back to the previous screen - nothing will be saved
- Close - will close all pop-ups- nothing will be saved
- Save will save values and send you back to the previous screen
Now you can repeat the process and create as many levels in your hierarchy you like.
It is essential to notice that when you select where you want to add allowed values for a level, you can only choose those underlined in the tree structure. In this example, we need to set the allowed values for Level4. Therefore it is only the Level3 values that are selectable (underlined).
You can at any time edit your Hierarchy Custom Fields.
You can edit all the settings and you can edit all the Allowed Values.
You can even remove Allowed Values you don't need anymore. But you can only remove Allowed Values that do not have children.
DELETE A HIERARCHY CUSTOM FIELD
If you want to delete a Hierarchy Custom Field - you have to be careful.
Because if the Hierarchy Custom Field you want to delete has sub-levels - these will be deleted too. This is why any deletion of Hierarchy Custom Fields requires you to confirm the delete operation twice.
When you do delete a Hierarchy Custom Field - it deletes all its Allowed values and all sub-levels. So potentially you can lose a lot of data by just deleting one single Custom Field!
It is possible to use an API to send Hiearachy Allowed Values to Delogue. If you use this option, you should not create or change the values in Admin.
Read here for the documentation for how you set up the import of your Hierarchy Custom Fields: Read the documentation
USE THE VALUES ON THE STYLE LEVEL
Read here how you use your Hierarchy Custom Fields on style level: User Hierarchy Custom Fields on Style level