Configure Mapped Picklists

Mapped Picklists allows you to decide the options displayed in a picklist field based on the option selected in another picklist field. Mapped picklist involves two picklist fields, one the parent picklist field and the other the child picklist field. The option selected in the parent picklist decides the options to be listed in the child picklist.

For example, consider two fields: Line and Machine, in a custom module called System Breakdown, where a user needs to report a broken machine. In a complex setup with many lines and machines, a mapped picklist helps avoid confusion. The Line field is mapped to the Machine field so that when a user selects a line, only the machines linked to that line are shown. For instance, selecting Line 1 shows Machines A, B, C, D, and E, while Line 2 shows Machines V, W, X, Y, and Z.

Limitations while configuring Mapped Picklists

Only a Normal Picklist can be selected as a Parent Picklist.
Both the Normal Picklist and Multi Select Picklist can be selected as the Child Picklist.

Configuring a Mapped Picklist

Mapped picklists are configured at the model/module level. Follow the steps below to configure them.

Note: Before proceeding to configure mapped picklists, make sure you've created the required fields with the corresponding options.

Access the Developer Application.
Open the information page of the required device model, asset model, location model, or custom module.
In the left pane, select Fields.
Select the Map Field Dependency tab.
Click Add New Field.
Select the field that will act as the parent field (the field that dictates the available options in the child field).
Select the child field in which options should be dynamically updated.
Click Next.
In the mapping screen, parent field options appear in the top row, and child field options appear below them. Select which child options should be available for each parent option.
Click Save.

A mapped picklist is now created.