Difference between revisions of "Dependent Picklist"

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


;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.
:*A field cannot be deleted if it is a "parent" for a dependent field
:*A field cannot be deleted if it is the triggering value for a dependent field.
:*If the "parent" field of a dependent field is changed, a confirmation message appears, requesting the user to acknowledge that data will be lost if the change is executed
:*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.
:*Dependent picklist values cannot be reordered
:*Values in a dependent picklist can be sorted alphabetically, but they can't be manually ordered.
:*It is not possible to specify a default value for a dependent picklist.
:*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:29, 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. Some other value in the record (a trigger value) then determines which of those choices are available for the user to select.

For example, __TBD__

Adding a Dependent Picklist

For each Dependent Picklist, a "parent" field is selected, which defines the top-level field in the dependency hierarchy. Additional values ("child" fields) are defined within the dependent picklist. The resulting dependent picklist is created by associating "child" field(s) with each "parent" field.

This is a two-step process; first, create the "parent" field, then create the Dependent Picklist (the "child" field).

  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.

Using a Dependent Picklist

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.
  • 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.
  • 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