Difference between revisions of "Dependent Picklist"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 2: Line 2:


===About Dependent Picklists===
===About Dependent Picklists===
A Dependent Picklist can be based on a set of [[Radio Buttons]] or a standard [[Picklist]]. Some other value in the record (a ''trigger value'') then determines which of those choices are available for the user to select.
A Dependent Picklist can be based on a set of [[Radio Buttons]] or a standard [[Picklist]]. When the user selects a value from that list (the ''triggering value''), that choice  determines which values are present in the dependent picklist.


For example, {{TBD|}}
For example, {{TBD|}}


===Adding a Dependent Picklist===
===Adding a Dependent Picklist===
This is a two-step process; first, create the triggering field (also known as the ''parent'' field). Then create the Dependent Picklist.
This is a two-step process; first, create the triggering field (also known as the ''parent'' field). Then, for each possible selection in the triggering field, you specify which values appear in the dependent picklist.


#Using the instructions in [[Fields]], create a new field of any of the following types, add picklist values and save the field (this will be used as the parent field):
#Using the instructions in [[Fields]], create a new field of any of the following types, add picklist values and save the field (this will be used as the parent field):
Line 26: Line 26:
#* Click the '''[Add Associations]''' button.
#* Click the '''[Add Associations]''' button.
#* Choose the Dependent Picklist Values to be associated with each Parent Value.
#* Choose the Dependent Picklist Values to be associated with each Parent Value.
===Using a Dependent Picklist===


;Considerations:
;Considerations:
:*After a dependent field association is created, the ''Use Label for grouping'' option cannot be enabled for any of the parent or dependent field values.
:*After a dependent field association is created, the ''Use Label for grouping'' option cannot be enabled for any of the parent or dependent field values. {{TBD|huh?}}
:*A field cannot be deleted if it is the triggering value for a dependent field.
:*A field cannot be deleted if it is the triggering value for a dependent field.
:*If the triggering field for a dependent field is changed, a message appears telling you that data will be lost if the change is executed. Confirmation is required to proceed.
:*If the triggering field for a dependent field is changed, a message appears telling you that data will be lost if the change is executed. Confirmation is required to proceed.
{{TBD|Move these up:
:*Values in a dependent picklist can be sorted alphabetically, but they can't be manually ordered.
:*Values in a dependent picklist can be sorted alphabetically, but they can't be manually ordered.
:*It is possible to specify that the first value in the list of values is always the default. Otherwise, there is no default.
:*It is possible to specify that the first value in the list of values is always the default. Otherwise, there is no default.
}}
<noinclude>
<noinclude>
:''Learn more:'' [[Enumerated Fields]]
:''Learn more:'' [[Enumerated Fields]]
</noinclude>
</noinclude>

Revision as of 20:36, 2 May 2014

A Dependent Picklist lets you change the list of available choices, based on some other value.

About Dependent Picklists

A Dependent Picklist can be based on a set of Radio Buttons or a standard Picklist. When the user selects a value from that list (the triggering value), that choice determines which values are present in the dependent picklist.

For example, __TBD__

Adding a Dependent Picklist

This is a two-step process; first, create the triggering field (also known as the parent field). Then, for each possible selection in the triggering field, you specify which values appear in the dependent picklist.

  1. Using the instructions in Fields, create a new field of any of the following types, add picklist values and save the field (this will be used as the parent field):
  2. Using the instructions in Fields, create a new field of type: Dependent Picklist, and enter the following information:
    Label
    The field label that will be displayed
    Display Type
    Dependent Picklist
    Parent Field
    • Select the "parent" field (created in the previous step)
    • Enter the picklist values
    Optionally, modify any of the remaining sections, using the instructions in Fields
  3. Click [Save]
  4. In the Enumerated Values section, click [Manage Values] to specify the collection of all possible values.
  5. In the Dependent Picklist Associations section (at the bottom):
    • Click the [Add Associations] button.
    • Choose the Dependent Picklist Values to be associated with each Parent Value.
Considerations
  • After a dependent field association is created, the Use Label for grouping option cannot be enabled for any of the parent or dependent field values. __TBD: huh?__
  • A field cannot be deleted if it is the triggering value for a dependent field.
  • If the triggering field for a dependent field is changed, a message appears telling you that data will be lost if the change is executed. Confirmation is required to proceed.

__TBD: Move these up:

  • Values in a dependent picklist can be sorted alphabetically, but they can't be manually ordered.
  • It is possible to specify that the first value in the list of values is always the default. Otherwise, there is no default.

__

Learn more: Enumerated Fields