Skip to main content
2 risposte
  1. 13 mag 2011, 04:07

     

    Dependent Picklist Considerations

    Available in: All Editions

     

    User Permissions Needed To define and edit dependent picklists: “Customize Application”

    Consider the following when defining dependent picklists:

    CheckboxesCheckbox fields can be controlling fields but not dependent fields.Converting fieldsConvert your existing fields to dependent picklists or controlling fields without affecting the existing values in your records. Going forward, dependency rules apply to any changes to existing records or new records.Default valuesYou can set default values for controlling fields but not for dependent picklists.Field-level securityField-level security settings for a controlling field and dependent picklist are completely independent. Remember to hide controlling fields whenever its correlating dependent picklist is hidden.ImportThe import wizards do not consider field dependencies. Any value can be imported into a dependent picklist regardless of the value imported for a controlling field.Lead conversionIf you create a dependency for lead fields that map to account, contact, and opportunity fields for lead conversion, create the same dependency on the account, contact, or opportunity as well.Dependent picklists and controlling lead fields can be mapped to account, contact, or opportunity fields with different dependency rules. Multi-select picklistsMulti-select picklists can be dependent picklists but not controlling fields.Connect OfflineWhile controlling fields and dependent picklists are available in Connect Offline, the logic between them is not.Page layoutsMake sure controlling fields exist on any page layout that contains their associated dependent picklist. When the controlling field is not on the same page layout, the dependent picklist shows no available values.For visually-impaired users, make sure the dependent picklist is lower on the page layout than its controlling field.If a dependent picklist is required and no values are available for it based on the controlling field value, users can save the record without entering a value. The record is saved with no value for that field.Picklist limitationsCustom picklist fields can be either controlling or dependent fields.Standard picklist fields can be controlling fields but not dependent fields.The maximum number of values allowed in a controlling field is 300. In addition, if a field is both a controlling field and dependent picklist, it can't contain more than 300 values.Before defining a dependency, make sure your picklist has at least one value; standard fields like Product Family do not contain any values until you add them.If a standard controlling field relies on functionality that your organization decides to disable, the dependency rules for the picklist will go away. For example, if your organization disables the Self-Service portal and the Closed by Self-Service User is a controlling field, its dependent picklist will display all available values.The following fields are not available as controlling fields:Activity FieldsCall TypeCreate recurring series of eventsShow Time AsSubjectTaskTypeContact FieldsSalutationContact CurrencyCustom Object FieldsCurrencyLead FieldsConvertedUnread By Owner Record typesThe values in your controlling fields are determined by the record type selected. The values in your dependent picklists are determined by the record type and controlling field value selected. In short, the values available in dependent picklists are an intersection of the record type and controlling field selections. For more information on record types, see

    Managing Record Types.