Manage Your Picklist Values

Are you still thinking about cookies from that last challenge? There are so many flavors of cookies in the world. If you’re running a cookie company, you want to standardize your flavor names. Are your cinnamon cookies called “snickerdoodles”? Once you pick the name, you want to make sure your orders, and other records, always use the same name.

We show you how to get smart about how you set the values for picklists. Good picklist value management saves you time and helps keep the data in your org consistent.

Picklists are fields associated with individual objects. You set and manage picklists in the same place you add or manage other fields: an object’s Fields & Relationships page. When you created your picklist in the last unit, you set its initial values. Let’s go back and look at a Fields & Relationships page.

What does “Indexed” mean? The page of Fields & Relationships identifies some fields, including some picklists, as indexed and you’re probably wondering what that means. An indexed field is stored in the database in a way that supports quick retrieval. This optimizes report generation, list views, and other requests…sometimes. What makes a good index candidate is pretty advanced. Salesforce automatically analyzes performance and periodically assigns fields to be indexed. You don’t have to think about this while you’re creating picklists, but it can be important later if you’re trying to optimize report or org performance.

1. In Setup, click the Object Manager tab, and then select the object associated with your picklist field.
2. Click Fields & Relationships.
3. Click the picklist’s Field Label to see the field’s detail page. You see your values in the Values related list 

You have a few options on this page:

Remember, sometimes standard picklist fields share a standard value set. When you change a value in that set, the change also appears in other standard picklist fields that use the same values. For example, the Lead Source and Account Source standard picklist fields share the same value set. Change standard picklist field values carefully.

• New: Create a new value.
• Reorder: Rearrange the existing values.
• Replace: Replace an existing value. You can replace an existing value with a new value, one of the other values, or a blank value. If you replace an existing value with a blank value, existing records will not display the value anymore.
• Printable View: See all of your values at once. This is a helpful view while you set up a dependent picklist.
• Chart Colors: Customize the appearance of values on charts and reports.

In the Values related list on the detail page, you can edit, delete, or deactivate individual values. You can probably guess the difference between an active value and an inactive one. Active values appear as an option in a picklist. Inactive values don’t, but they’re not entirely removed from your org.

When is this helpful? Think about your delicious pumpkin cookies. They aren’t popular in summer, so you set that value to inactive all summer. In the fall, customers want pumpkin-flavored everything, so you start making pumpkin cookies and set the value to active, again.

But sometimes you really no longer need a value. You tried selling spinach cookies. Surprisingly, these were not a hit with your customers, so you delete that value.

Let’s look at the Values related list.

On the field’s detail page, click Edit to see more options for a single value.

It’s easy to overlook the API name because it’s auto-populated when you create the field. But this value is incredibly powerful. The API name is a unique identifier for a value, even when the label changes.

Since the Spring ’17 release, picklist values are assigned an API name, which is a reference to the value, as well as a label, which is what shows in the UI. The API name allows formulas and custom apps to refer to a picklist value, even if the field name changes.

Imagine writing a formula, or customizing an app that refers to a picklist label value (as admins and devs had to do before Spring ’17). Then the picklist value changes, and now the formula or reference to that value is no longer valid. Change happens. But, references to the API name continue to be valid, no matter the label value. And you can prevent the API name from changing to ensure references to the field’s value won’t become invalid, later.

As we discussed in the previous unit, dependent picklist fields narrow the available values based on a selection in a controlling field. For example, the user selects “nut free” in a controlling field, and only cookie flavors that don’t have nuts show in the dependent picklist field.

The controlling field doesn’t have to be a picklist. It can also be a checkbox.

Some things to consider:

• Custom picklist fields can be either controlling or dependent fields.
• Standard picklist fields can be controlling fields, but not dependent fields.
• Multi-select picklist fields can be dependent, but not controlling fields.
• You can set default values for controlling fields but not for dependent picklists.
• If your org uses record types, choose a record type to test how it affects your controlling and dependent picklist values. The record type and the controlling field together determine what values are available in the dependent picklist. For example, a dependent value is only available if it’s available in the selected record type and the selected controlling value.

1. In Setup, click the Object Manager tab, and then select the object associated with your picklist field.
2. Click Fields & Relationships.
3. Click Edit next to the picklist field. 
4. Add your formula under General Options. 
5. Click Save.

It’s super helpful to click Show Formula Editor so you have more space.

More importantly, the Formula Editor lets you check your syntax and gives you picklists (Yay picklists!) to suggest fields, operators, and functions for your formula.

Define something for the value default in case the formula doesn’t resolve to an active value. For example, the following is a formula to set an Opportunity priority to High for all users in the Fast Response Sales profile. Otherwise, the value is Standard.

IF($Profile.Name = "Fast Response Sales", "High", "Standard")

If you want the field to remain blank when the user isn’t in the Fast Response Sales profile, use:

IF($Profile.Name = "Fast Response Sales", "High", null)

1. In Setup, click the Object Manager tab, and then select the object associated with your picklist field.
2. Click Fields & Relationships.
3. Click Edit next to the picklist field.
4. Select Change Field Type. 
   

Inactive values will be lost.

And vice-versa. You can convert a multi-select picklist to a custom picklist that doesn’t allow multi-selection by changing the field type.

When you change a multi-select picklist to a picklist that doesn’t allow multi-selection, Salesforce clears the values for that field on existing records. This makes sense, right? Because the field now only allows one value.

You can see that you have a lot of flexibility managing picklist values, and even the type of picklist to use. You can start with one type of picklist and switch to another, or change the behavior of the values in a picklist. It helps that you don’t have to have it all figured out in advance. Change the picklist properties to meet your needs. In the next unit, you learn to share picklist values with more than one picklist.