Require Field Input to Ensure Data Quality

A universally required field is a custom field. It must have a value whenever a record is saved within Salesforce, the Lightning Platform API, Connect Offline, Salesforce for Outlook, the Self-Service portal, or automated processes, such as Web-to-Lead and Web-to-Case. Making a field required on a page layout or through field-level security ensures that users must enter a value. Making a field required universally gives you a higher level of data quality beyond the presentation level of page layouts.

You can make these types of custom fields universally required:

• Currency
• Date
• Date/Time
• Email
• Master-Detail Relationship (always required)
• Number
• Percent
• Phone
• Picklist
• Text
• Text Area
• URL

To make a custom field universally required, select the Required checkbox when defining the custom field.

Note You must specify a default value for required campaign member custom fields.

If you make a user field universally required, you must specify a default value for that field.

Relationship group members don’t support universally required fields.

• Considerations for Universally Required Fields
  A universally required field is a custom field. It must have a value whenever a record is saved within Salesforce, the Lightning Platform API, Connect Offline, Salesforce for Outlook, the Self-Service portal, or automated processes such as Web-to-Lead and Web-to-Case. Review the following considerations before making your custom fields universally required.