| Print Open PDF Version of Online Help

#### Setting Up Shared Cascading Picklists On the record types that support sharing picklist values, you can set up cascading picklists that share the configuration of existing cascading picklists on a different record type. The record type where the original cascading picklists are defined is referred to as the source record type, and the record type that shares the configuration of the original cascading picklists is referred to as the destination record type. For example, you might want to set up cascading picklists on the Account record type so that they have the same picklist values and the same associations between the values as cascading picklists that are already set up on the Contact record type. In this example, the Contact record type is the source record type, and the Account record type is the destination record type. For a list of the record types that support sharing picklist values, see Creating Custom Picklist Fields with Shared Values. To set up shared cascading picklists, perform the steps in the following procedure. Before you begin. The cascading picklists on the source record type must already be set up. To set up shared cascading picklists In the record type Fields page for the destination record type, create custom picklist fields that take their values from the picklist fields that are used in the cascading picklists on the source record type. For example, if the cascading picklists on the Contact record type use a field named Class as the parent picklist and a field named Subclass as the related picklist, then do the following on the Account record type: Create a custom picklist field and configure it to take its values from the Class field on the Contact record type. Create a second custom picklist field and configure it to take its values from the Subclass field on the Contact record type. NOTE: For information about creating picklist fields that take their values from other picklist fields, see Creating Custom Picklist Fields with Shared Values. In the record type Application Customisation page for the destination record type, click the required Cascading Picklists link, and then do the following: In Step 1 of the Cascading Picklist Setup page, in the Parent Picklist and Related Picklist fields, select the custom picklist fields that you set up in step 1 of this procedure, and optionally enter a description of the cascading picklists. Make sure that the relationship between the parent picklist and the related picklist is the same as the relationship between the corresponding fields on the source record type. In the example used earlier, the Class field is used as the parent picklist in the cascading picklists on the Contact record type, and the Subclass field is used as the related picklist. Therefore, in the cascading picklists on the Account record type, the field that takes its values from the Class field on the Contact record type must be the parent picklist and the field that takes its values from the Subclass field on the Contact record type must be the related picklist. In Step 2 of the Cascading Picklist Setup page, select the Enable Shared Cascading Picklist check box. After you select this check box, the page shows the associations that are already set up between the parent values and the related values in the cascading picklists on the source record type, and you cannot change the associations. Click Finish to save the cascading picklists definition. If any of the values in the source fields are later changed, then the same changes are automatically reflected in the destination fields. Similarly, if any of the associations between the parent values and the related values in the cascading picklists on the source record type are changed, then the same changes are automatically reflected in the cascading picklists on the destination record type. If you later deselect the Enable Shared Cascading Picklist check box on the cascading picklists, then the associations between the parent values and the related values become editable, and the cascading picklists no longer share the configuration of the cascading picklists on the source record type. Therefore, if any of the associations are later changed in the cascading picklists on the source record type, then the changes are not reflected in these cascading picklists. However, the custom picklist fields on the destination record type continue to take their values from the picklist fields on the source record type, unless you change the configuration of the fields so that they no longer take their values from the picklist fields on the source record type.

Published August 2022 | Copyright © 2005, 2022, Oracle and/or its affiliates. Legal Notices.