Certain attribute input types allow a list of values to be defined. When a list of values has been defined, users must choose one or more values from this list when populating the attribute (either through manual edits or imports).
In order to use a defined list, the attribute input type must be one of the valid list-types (i.e. single select, multi select, combo or multi combo). For more information on these input types, see Attribute input types.
Once a valid input type has been selected, the 'Values' field will be available
Selecting the Values field will show the Multi Select Config dialog, where you can choose between an ad hoc list of values or linking the attribute to an existing data set
Ad Hoc Lists
Ad hoc lists are useful where there are only a few values to choose from. Any number of values can be added (along with a corresponding label for each value), but these can be tricky to maintain for large numbers of values.
A new value can be added by entering the desired label and value in the 'Option label' and 'Option value' field and selecting the plus button.
To remove a value, simply select the minus button next to the value you wish to delete.
Data sets are useful for handling larger numbers of values, as well as being able to filter the values that are shown based on the value of a different attribute.
A data set must already exist in the system to be able to link this to an attribute. Management of data sets must be done through the Data Sets screen (Settings - Data Sets), values cannot be added, edited or removed through the attribute setup screens.
When choosing to use a data set, a number of options are configurable:
- Data set - The existing data set which is being used to create the list of values
- Value column - The column heading in the data set spreadsheet which contains the list of values to be used
- Label column (optional) - The column heading in the data set spreadsheet which contains the list of labels corresponding to the values being used. This can be left empty if the labels are the same as the values
- Filter column (optional) - The column heading in the data set which is used to filter the values available for selection
- Filter attribute - The attribute in Pimberly which contains the value from the filter column; this dictates the values that will be shown for selection
For example, different clothing brands have different names for the colours they offer. In a data set, this may look like the following:
|Brand||Colour Name||Colour Value|
|French Quarter||Skye Bleu||B359S|
|French Quarter||Jolie Pink||P468J|
|French Quarter||Rouge Blush||B831R|
|French Quarter||Violet Creme||C483V|
|Jeff Daisington||Canary Yellow||YE8442|
|Jeff Daisington||Indigo Blue||BL6121|
|Jeff Daisington||Racing Green||GR3345|
|Jeff Daisington||Purple Jewel||PU7300|
|K L Feinmann||Shocking Pink||P1NKS|
|K L Feinmann||Orange Blossom||0R4N6|
|K L Feinmann||Vanilla Cream||V4N1L|
|K L Feinmann||Mocha||M0CH4|
The list of clothing brands has been set up in the attribute 'PIM-216 Brand'. I would like the colour selection to appear in the 'Colour' attribute and the choice of colours to be based on the clothing brand that has been chosen. I would also like the value and label to both use the 'Colour Name'.
In this scenario, I would set up the data set configuration as follows:
When editing a product, if a user selects 'K L Feinmann' in the Brand attribute, the Colours attribute will now only show the options related to that brand, i.e. 'Shocking Pink', 'Orange Blossom', 'Vanilla Cream' and 'Mocha'.
Note: When importing data to an attribute that uses a data set, the import file must contain the data set values, not the labels.
Editing List Values
Ad hoc value lists can be edited within the Multi Select Config screen. Data set values can only be edited through the Data Sets screen.
Changing or removing a value from a list will not change the value in any attributes where this value has already been selected. The user will be prompted to select a valid value when the product is next edited.