Required and Read-Only Fields in Dynamic Forms

A field set to Required in the field definition in the Object Manager is a universally required field. Its Required value isn’t editable in the field’s properties in the Lightning App Builder property panel. Also, the required or read-only status of some standard fields—such as Created By, Last Modified By, Owner, and Record Type—can’t be changed in the Lightning App Builder property panel.

Fields marked as Required or Read-Only on a page layout retain that state when migrated into a Dynamic Forms-based page.

You can find all universally required fields for your page in the Universally Required Fields section of the Fields palette. Fields that you make required at the page layout level or in the Lightning App Builder property panel don’t appear in the Universally Required Fields section of the palette.

If you set a field on a Lightning page to Required or Read-Only in the Lightning App Builder property panel, the behavior applies only to the field on that page, not to all instances of the field.

If a field is set to Required in the Lightning App Builder, it’s hidden by a visibility rule at run time, and users can save the record even if that field isn't populated.

Be sure to include universally required fields on your Lightning pages that are used for creating or editing records. They aren’t added automatically. If required fields are missing from the page, and the missing required fields don't have values, users can’t save a record after editing, creating, or cloning it.

Don’t hide universally required fields with visibility filters. Users can’t save a record if values are missing in any universally required field, even if they’re hidden by a visibility rule.