Picklist Field
The Picklist field type allows users to select a value from a list you define. Several other field types (multi-select picklists, radio buttons and group of checkboxes) have a similar configuration. You can define the following properties:
-
Field Properties
-
Field Label — (mandatory) is displayed on the left from the field on view, edit, and new record pages.
-
View Header — (optional) is used in headers of views and reports. If not specified, the Field Label is used.
-
View Width — (optional) is used to set width (in pixels or %) of columns in views and reports. If not specified, the browser calculates the width of columns automatically.
-
Shared As — In some situations, you might want picklists belonging to different objects to have the same set of values. Platform allows you to share picklists among those objects. To share a picklist, select Share as New from the Shared As drop-down when you create the picklist.
To use values from an existing shared picklist, select the integration name of the shared picklist from the Shared As drop-down when you create the picklist. The content of the Values box is replaced with existing values from the selected shared picklist.
Any picklists belonging to different objects to have the same set of values are shared among those objects. The shared picklist can be viewed in a section under the Application Setup page.
Note:- The Shared Picklist section displays a list of all distinct shared picklists used across all objects within this application.
- Unlike other components such as objects and tabs, Shared Picklists cannot be attached or detached from the application settings page. Instead, their presence is deduced from the list of attached objects.
- In cases where multiple fields across different objects are mapped to the same shared picklist data, the Shared Picklist section reflects this information under the Usage column.
- The Shared Picklist section will display the ID and Label from any one field when there are multiple usages of the same shared picklist data. This helps streamline and clarify the representation of shared picklist information.
-
Values
-
Add Value
A list of available options for any newly added value includes:
-
Delete: Deletes the particular value from the list.
-
Move up: Moves the value one level up in the picklist order.
-
Move down: Moves the value one level down in the picklist order.
-
Add: Select if you want to add a row above or below the selected picklist value.
-
Deployed: Select if you want the particular value to be seen while creating records from the application's list view.
-
Default: Select if you want the particular value to be set as default for new records.
-
Name: The name of the value. This is a mandatory field.
-
Code: The integration code of the given value.
-
Language: The name of the value based on set additional language.
-
-
Bulk Add Values:
First, define a list of values, one value per line, for the picklist. Each value represents a selectable item. The length of a picklist value cannot exceed 100 characters. If you want a particular value to be selected by default for new records, prefix it with {D}.
Optionally, at the end of each line, add | followed by an integration name for that value (no longer than 40 characters). Formulas and APIs can use this integration name to access unique picklist values (e.g., for data import and export).
Example: In the following list of picklist values, each value is assigned an integration name and Yes is the default value:
Note:- Bulk Add option cannot be used to edit any existing values.
- Adding names corresponding to additional languages are not supported in Bulk Add option.
-
-
Letters are not case-sensitive — See Configuring picklist case-sensitivity for more information.
-
Sort values alphabetically, not in the order entered — You can also choose whether to display values sorted alphabetically (the default) or in the order the values were entered.
-
Use value instead of integration code for Export and Reports — Enable to use display name instead of Integration code.
-
Assign values for all existing object records now — Enable to assign this field to all existing Object records once it is created or updated.
-
Exclude items to be added in picklist from import — Enable if you want to restrict the scope of import to lookup possible picklist values from already entered list. With this, no new picklist option are created and assigned on the fly based on non-matching inputs from the import payload. Also, when checked at field level, no new picklist items are created during import.
-
-
Advanced Field Properties — For more information, see Advanced field properties.
-
Integration Name — The integration name is used to reference this field via merge fields or with Platform APIs.
-
Field-Level Help — The Field-Level Help box allows you to define help text for the field that will appear in a popup when the user clicks the help icon next to the field.
- From Platform 6.5 onwards, Application XML generation, installation, or push updating would be blocked if any duplicate labels or integration codes exist in the picklist items.
- You may still proceed with any of the above mentioned operation with duplicate integration codes. This is governed by shared property - SkipUniquePicklistCodesCheck. Tenant administrators can enable the same using the Skip unique codes check on picklist option from the Administrative Preferences section.
Editing picklists
The following rules and behaviors apply when editing picklists:
- You cannot change the integration name of a shared picklist. All picklists that share the same values have the same integration name.
- If you delete the text value of a picklist item, existing records will lose their assigned values.
- Shared picklists share the same text values for their picklist items. If you delete the text value from one shared picklist, that value is deleted from all of the picklists that share with it.
Configuring picklist case-sensitivity
The picklist property page includes an option Letters are not case-sensitive. This allows the picklist field value to evade case-sensitivity. While the default value for the existing picklist fields remains as false
, for every new picklist field created, this value is set to true
by default.
-
The following can be the recommended path to configure the picklist field from case-sensitive to case-insensitive:
-
The Tenant Admin should ensure that the picklist field does not have any existing conflicting labels.
-
For any existing duplicate labels (case-insensitive), ensure a manual clean up to avoid any loss of data.
-
You can also manually promote the existing field to case-insensitive configuration via the metadata Edit page.
-
Viewing a Picklist
The entire set of values pertaining to any Picklist available for lookup within a tabular section in the Field View page. The table specifies the ID, Original ID, Order Number, Values, Code and Default for every picklist item.