In Developer Studio, you set the type of dimension value handling, on a per mapping basis, by selecting a mode from the Match mode list in the Dimension Mapping editor, as illustrated below:
There are three match modes you can choose from:
Note
Match modes only apply to dimensions. They are not used when mapping source properties to Guided Search properties.
Normal match mode maps only those source property values that have a matching dimension value explicitly defined in the dimension hierarchy.
Forge assigns the IDs for any matching dimension values to the Guided Search records. Any source property values that do not have matching dimension values in the dimension hierarchy are ignored.
In order for a source property value to match a dimension value, the dimension value’s definition must contain a synonym that:
Must Match behaves identically to Normal, with the exception that Must Match issues a warning for any source property values that do not have matching dimension values.
Related links
Auto Generate specifies that Forge automatically generates a dimension value name and ID for any source property value that does not have a matching dimension value in the dimension hierarchy. Forge uses these automatically-generated names and IDs to tag the Guided Search records the same as it would explicitly-defined dimension values.
Auto Generate mode dramatically reduces the amount of editing you have to do to the dimension hierarchy. However, auto-generated dimensions are always flat. Auto-generated names and IDs are persisted in a file that you specify as part of a dimension server component.
Related links
