---
schema_version: "1"
id: f02af4ffe7664644c0da226edb18822ec95130b81d5cdd9c323d85654ed176c1
title: Required and Read-Only Fields in Dynamic Forms
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/dynamic_forms_req_fields.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.dynamic_forms_req_fields.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0ae11a7de07ec383802cd74b871192631cf7948b56d9b39e09def75410521fa3
description: Universally required fields retain their status when you’re working with them on a Dynamic Forms-based Lightning page. But you can make other fields required or read-only just for the page that you’re working on.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Required and Read-Only Fields in Dynamic Forms

Universally required fields retain their status when you’re working with them on a Dynamic Forms-based Lightning page. But you can make other fields required or read-only just for the page that you’re working on.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Lightning App Builder available in: Salesforce Classic (not available in all
            orgs) and Lightning Experience</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Lightning pages and Dynamic Forms available in: Lightning Experience and the
            Salesforce mobile app</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p style="margin-bottom:0;">Available in: <strong>Group</strong>
              <strong>Essentials</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>,
              <strong>Unlimited</strong>, and <strong>Developer</strong> Editions
            </p>
          </td>

        </tr>
      </tbody>
    </table>

## Universally Required Fields

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.

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 universally 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.

## Page-Level Required or Read-Only Fields

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 when it appears on that page, not to all instances of the field.

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

#### See Also

- [Break Up Your Record Details with Dynamic Forms](https://help.salesforce.com/s/articleView?id=platform.dynamic_forms_overview.htm&release=264.0.0&type=5 "The more fields that there are on your page layout, the more that the Record Detail component becomes a monolithic block of fields that you can’t customize. With Dynamic Forms, you can migrate the fields and sections from your page layout to individual components in Lightning App Builder. Then you can configure them the same way as the other components on the page - spreading them out across multiple columns and tabs, and dynamically showing and hiding them based on record data, user details, and device type, so that your users get only the fields and sections that they want.")
- [Require Field Input to Ensure Data Quality](https://help.salesforce.com/s/articleView?id=platform.fields_about_universally_required_fields.htm&release=264.0.0&type=5 "Improve the quality of data that users enter in Salesforce by creating universally required fields.")
- [Considerations for Universally Required Fields](https://help.salesforce.com/s/articleView?id=platform.fields_universally_required_field_considerations.htm&release=264.0.0&type=5 "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.")