Managing Picklist Dependencies

Dependent picklists are a powerful configuration option and should be carefully mapped out during the design phase to ensure easy maintenance. Once implemented, this option can make field entry simpler and more consistent for users. You can configure dependent picklists on objects and documents.

Typically, picklist dependencies for objects are configured on Picklist object fields. For example, if you select Use existing picklist and choose a product sub-category picklist, the dependencies on the field indicate which options from the reused picklist are available based on selections from a controlling field that reuses a product category picklist. In this case, the dependencies exist on the Picklist field and not the picklist itself. This allows different Picklist fields that reuse the same picklist to use differing dependencies.

Standard and System-Managed Picklists for Objects

Some Standard and System-managed picklists controlled by Veeva may contain dependencies which exist on the picklist itself rather than the Picklist field. When reused in a Picklist field, these dependencies remain the same, as opposed to Picklist field dependencies where dependencies can vary across Picklist fields despite reuse of the same picklist.

When interacting with Veeva-controlled Standard and System-managed picklist dependencies, take the following information into consideration:

• If you select Use existing picklist when creating a Picklist field, and select a Standard or System picklist with dependencies, ensure that a Picklist field exists on the object that reuses the corresponding controlling picklist. Vault prompts you to select the Controlling Field when you select the dependent picklist. For example, if you use the State picklist, you must first configure another field on the object to reference the controlling Country picklist. You can only use dependent Standard and System-managed picklists in conjunction with their controlling picklist. However, you can use a Standard or System-managed controlling picklist in a Picklist object field independent of its dependent picklist.

• You cannot modify Standard and System-managed picklist dependencies.

• If a Picklist field reuses a dependent Standard or System-managed picklist, you cannot add object-level dependencies to the Picklist field. Picklist fields must be bound by a single set of dependencies, either defined on a Standard or System-managed picklist or on the Picklist field itself.

• You can create dependencies on Standard and System-managed picklists as long as they do not have an existing Standard or System-managed picklist dependency in place.

• You can create a picklist dependency on a custom object field that references a Standard or System-managed picklist.