Define Default Values at the Field Level

Up until now, the same default field value applied for all users, and to change it, you had to update the default from Setup. Now you can also define a default value at the field level. The new field-level default has precedence over the values-level default. The field-level default value can be a constant or a formula.
Available in: All Editions

Let’s say you want a custom picklist field on an Opportunity object to track the priority of a particular opportunity. In addition, you want to have a default priority for the opportunities that are being created.

High, medium, and low priorities where medium is the default.

But what if you want to set up a different default priority for another group of users? Imagine that you have a fast response sales team in your org. You want all opportunities created by them to be treated with a higher priority. It’s now possible with new formula-based default field values. To add a default value formula:

An example formula for a picklist default.
So, if the user profile is Fast Response Sales, then priority is set to High, but for everyone else it remains Medium. How is this magic possible? It’s possible because now we have two levels of default values:
  • Field-level default—Defined by the formula
  • Value-level default—The way you used to set up default values
When there’s no formula for a default value, or when a formula does not resolve to an existing value’s API name, the value-level default is applied. In our example, that’s how Medium remains the default for profiles other than Fast Response Sales.

The new formula-based default values also let you have different default values for each field that uses the same Global Value Set. Previously, all fields had the same value, defined on a value set. Now for different default values you just set up individual default formulas for each field.