Print      Open PDF Version of Online Help

Administering Oracle CRM On Demand > Application Customization > Record Type Application Customization Page > Creating Custom Picklist Fields with Shared Values

Creating Custom Picklist Fields with Shared Values

On certain record types, you can create a custom picklist field that takes its list of values from another picklist field on the same record type or on a different record type. The field from which the values are taken is referred to as the source field, and the field that shares the values from the source field is referred to as the destination field. You can set up multiple custom picklist fields as destination fields on the record types that support sharing picklist values.

When you first set up a destination field, the list of values in the field is automatically synchronized with the list of values in the source field. Any changes that you make to the list of values in the source field in the future also apply to the list of values in the destination field. For example, if you add a new value to the list of values in the source field at any time, then that value is available for selection in both the source field and the destination field. You cannot update the list of values in the destination field through any channel.

When setting up a custom picklist field as a destination field, note the following points:

• You cannot use a destination field as the source field for another picklist field.
• You can select any picklist field from any record type to use as the source field, provided that both of the following are true:
  • The source record type is one whose fields you can configure through the Application Customization pages in Oracle CRM On Demand.
  • The field that you want to use as the source field is not set up as a destination field.
• You can use a picklist field as the source field for multiple destination fields.
• If you change an existing custom picklist field that previously contained its own list of values and configure the field to take its values from another picklist field instead, then the values that were originally set up for the custom picklist field are deleted. However, records that reference the deleted values are not updated automatically. In such cases, the records show the Language Independent Code (LIC) of the picklist value that was deleted. It is recommended that you find any records that reference the deleted values and update the records as necessary to show valid values (or no value).
• If you change the configuration of an existing destination field so that the field no longer takes its list of values from another picklist field, then after you save your changes, the list of values for the custom picklist field initially contains the active values from the field that was previously used as the source field. However, the list of values in the custom picklist field becomes editable and you can add new values and disable values. Any changes that are later made to the list of values in the field that was previously used as the source field are no longer synchronized with the values in the custom picklist field.

The following record types support sharing picklist values:

• Account
• Account Contact
• Account Team
• Activity
• Campaign
• Claim
• Contact
• Contact Portfolio
• Contact Team
• Custom Objects
• Event
• Household Contact
• Insurance Property
• Invitee
• Involved Party
• Lead
• Lead Team
• Objective
• Opportunity
• Opportunity Product Revenue
• Opportunity Team
• Partner
• Policy
• Policy Holder
• Service Request
• Service Request Team
• Solution
• User

NOTE: You can optionally set up a custom field of the Picklist field type to act as a related information field, or you can optionally set it up to take its list of values from another picklist field, but you cannot set it up to do both. For information about creating custom related information fields, see Creating Custom Related Information Fields.

The following procedure describes how to create a custom picklist field that takes its values from another picklist field.

Before you begin. To perform this procedure, your role must include the Customize Application privilege.

To create a custom picklist field that takes its values from another picklist field

1. In the upper-right corner of any page, click the Admin global link.
2. In the Application Customization section, click the Application Customization link.
3. In the Record Types Setup section, click the link for the record type in which you want to set up the custom picklist field that will take its values from another field.
4. In the Field Management section, click record type Field Setup.
5. On the record type Fields page, click New Field.
6. On the record type Field Edit page, do the following:
   1. In the Display Name field, enter the name of the new field.
   2. In the Field Type field, select Picklist.
   3. Select the Enable Shared Picklist Values check box.
   4. In the Shared Record Type field, select the record type that contains the source field.
   5. In the field called Shared Field, select the name of the source field.
   6. Complete the remaining fields on the record type Field Edit page as required.
   7. Save the new custom picklist field.
7. (Optional) Enter a translation of the name of the new field, as follows:
   1. On the record type Fields page, from the Translation Language drop-down list, select the language whose translation you want to enter.
   2. Click the Edit link for the field whose name you want to translate.
   3. Enter the translation in the Display Name field, and click Save.

      The translated name appears in black text in the Display Name column.

      NOTE: You can also enter translations of the tooltip and description for the field.

   4. Repeat steps a through c for each language whose translation you want to enter.
   5. To continue working in the record type Fields page after you finish entering the translations, in the Language drop-down list, select the default language for your company.