Dependent Picklist Field

The Dependent Picklist Field type is a special type of single-select picklist that displays different available values depending on the current selection in another (main) picklist. This main picklist must be selected before creating a dependent picklist. A typical example of a dependent picklist is a list of States or Provinces that depends on the selection of a Country picklist. Once the selection in the Country picklist changes, Platform will automatically update the available list of states.

You can define the following properties:

  • Field Properties

    • Field Label — (mandatory) is displayed on the left from the field on view, edit, and new record pages.

    • View Header — (optional) is used in headers of views and reports. If not specified, the Field Label is used.

    • View Width — (optional) is used to set width (in pixels or %) of columns in views and reports. If not specified, the browser calculates the width of columns automatically.

    • Shared As — In some situations, you might want picklists belonging to different objects to have the same set of values. Platform allows you to share picklists among those objects. To share a picklist, select Share as New from the Shared As drop-down when you create the picklist.

      To use values from an existing shared picklist, select the integration name of the shared picklist from the Shared As drop-down when you create the picklist. The content of the Values box is replaced with existing values from the selected shared picklist.

      Picklist Share

    • Values

      • Add Value

        A list of available options for any newly added value includes:

        • Delete: Deletes the particular value from the list.

        • Move up: Moves the value one level up in the picklist order.

        • Move down: Moves the value one level down in the picklist order.

        • Default: Select if you want the particular value to be set as default for new records.

        • Name: The name of the value. This is a mandatory field.

        • Code: The integration code of the given value.

        • Language: The name of the value based on set additional language.

      • Bulk Add Values:

        For each value of the main picklist, you can enter a comma-separated list of available values as shown below. For each value of the main picklist, you can enter a comma-separated list of available values as shown below.

        Note:
        • Bulk Add option cannot be used to edit any existing values.
        • Adding names corresponding to additional languages are not supported in Bulk Add option.

    • Letters are not case-sensitive — See Configuring picklist case-sensitivity for more information.

    • Sort values alphabetically, not in the order entered — You can also choose whether to display values sorted alphabetically (the default) or in the order the values were entered.

    • Use value instead of integration code for Export and Reports — Enable to use display name instead of Integration code.

    • Assign values for all existing object records now — Enable to assign this field to all existing Object records once it is created or updated.

    • Exclude items to be added in picklist from import — Enable if you want to restrict the scope of import to lookup possible picklist values from already entered list. With this, no new picklist option are created and assigned on the fly based on non-matching inputs from the import payload. Also, when checked at field level, no new picklist items are created during import.

    • List Height — Choose a height (in rows) to determine the number of values visible at any given time. If more than one value is visible the user can use the CTRL key plus their mouse to select multiple items.

     
  • Advanced Field Properties — For more information, see Advanced field properties.

  • Integration Name — The integration name is used to reference this field via merge fields or with Platform APIs.

  • Field-Level Help — The Field-Level Help box allows you to define help text for the field that will appear in a popup when the user clicks the help icon next to the field.

Note:
  • For more information on configuring case-sensitivity of picklist field values, see Configuring picklist case-sensitivity.
  • From Platform 6.5 onwards, Application XML generation, installation, or push updating would be blocked if any duplicate labels or integration codes exist in the picklist items.
  • You may still proceed with any of the above mentioned operation with duplicate integration codes. This is governed by shared property - SkipUniquePicklistCodesCheck. Tenant administrators can enable the same using the Skip unique codes check on picklist option from the Administrative Preferences section.
Limitation: Each value in a dependent picklist may belong to only one value from the main picklist. If you need to re-use values in dependent picklists because one or more values needs to be associated with more than one value from the main picklist, you should instead create new Object definitions and use a lookup Field dependency. See the Relationships section below for more information regarding configuring relationship Lookup Fields to use Main and Link lookups to dynamically filter available selection choices.