Setting Up Shared Cascading PicklistsOn 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
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 6/21/2021 | Copyright © 2005, 2021, Oracle and/or its affiliates. Legal Notices. |