Salesforce · Lightning App Builder · Admin Guide

Salesforce Dynamic Forms: The Complete Guide to Record Page Customization

Dynamic Forms turn one long block of fields into sections you can place, require and hide on each Lightning record page. This guide covers how to migrate from page layouts, how visibility rules really behave, how to get mobile right, and the limits to plan for, all checked against Salesforce's own documentation.

How we checked this: every feature, limit and setting in this guide comes from Salesforce Help's Dynamic Forms and Lightning App Builder documentation, read on 22 October 2026. Salesforce changes these features with each release, so confirm the current behavior in Salesforce Help before a large rollout.

Key Takeaways

  • What it is: Dynamic Forms moves the fields and sections of a page layout into separate components in Lightning App Builder, so you can place them anywhere on a record page and show or hide each one with rules.
  • Where it works: custom objects and most LWC-enabled standard objects, in Group, Professional, Enterprise, Performance, Unlimited and Developer editions. Products, Events, Tasks and Notes are not supported.
  • The rule most teams miss: field rules react while a user edits, but section rules are only checked after the record is saved.
  • Not security: a hidden field still shows its data in reports, list views and dashboards. Use field-level security for access control.
  • Mobile: turn on "Dynamic Forms and Dynamic Highlights Panel on Mobile", then remove the Record Detail - Mobile component, or phone users never see your new layout.
  • Page layouts still matter: list view inline editing, path key fields and the printable view still read the page layout.

Salesforce Dynamic Forms solves a familiar problem. As an object grows, its record page turns into one long block of fields that every user sees, whether they need them or not. Teams answer that with more page layouts, more record types and more profiles to assign them to. Dynamic Forms takes another route. The fields stay on one Lightning record page, and the page decides what each user sees.

This guide is written for admins, architects and operations leaders at growing and mid-market companies who run Salesforce day to day. It replaces our 2022 guide with current Salesforce documentation: mobile support, the related Dynamic Actions and Highlights Panel features, documented limits, and a migration checklist.

Section 01 · Definition

What Are Salesforce Dynamic Forms?

Dynamic Forms is a Lightning App Builder feature that breaks the Record Detail component into separate Field and Field Section components. You place them anywhere on a Lightning record page, across columns and tabs, and show or hide each one with visibility rules based on record data, user details or device. Each user sees only the fields that matter to them.

Without Dynamic Forms, a record page shows its fields through one Record Detail component, and the content of that component comes from the page layout assigned to the user's profile and record type. With Dynamic Forms, the fields live on the Lightning page itself. Salesforce lists five benefits: fields and sections placed wherever you want, visibility rules, field management without the page layout editor, fewer page layouts and record types, and one assignment model (the Lightning page) instead of two (a page and a layout).

Field Section

A container for fields, with one or more columns, a label and expand and collapse. The building block that replaces the Record Detail component.

Field

A single field placed inside a Field Section. Each one can be set to Required or Read-Only for this page only, and carry its own visibility rule.

Blank Space

An empty slot that keeps fields aligned across columns. It counts toward the field limit in a section, not toward the page's component limit.

Dynamic Highlights Panel

A responsive header for up to 12 key fields, with visibility rules, conditional formatting and its own actions. Found on the Fields tab.

Dynamic Forms also changes more than the view. On a Dynamic Forms page, the fields users see when they create, edit or clone a record come from the fields on the page, not from the page layout. That is the point that makes the feature powerful, and it is also the source of most migration surprises.

Section 02 · Comparison

Dynamic Forms vs Page Layouts: What Actually Changes?

Page layouts decide which fields a user sees by profile and record type, and every user with the same assignment sees the same block. Dynamic Forms decides on the Lightning page, field by field, using any combination of record values, user attributes, permissions and device. One Dynamic Forms page can often replace several layouts, but layouts do not disappear.

QuestionPage layout + Record DetailDynamic Forms
Where fields are managedPage layout editorLightning App Builder
How users get a versionLightning page assignment plus a layout assigned by profile and record typeLightning page assignment only
PlacementOne block of fields in one componentSections anywhere on the page, including inside tabs and accordions
Show or hideOnly by giving the user a different layoutVisibility rules on each field and section
Required and Read-OnlySet on the layoutSet per page in the property panel; universally required fields stay required
Fields from related recordsNot in the detail blockCross-object fields from lookups, shown read-only
Create, edit and clone windowsFields from the layoutFields from the Lightning page
Still read from the layoutEverythingList view inline edit, path key fields, printable view and some create flows

Sources: Salesforce Help, Break Up Your Record Details with Dynamic Forms and Dynamic Forms Limitations, 22 October 2026.

Choose Dynamic Forms when the same object serves several teams that need different fields, or when the fields a user needs depend on the record's stage, type or values. Keep the page layout as the source of truth for the places Salesforce still reads it, and keep it tidy, because users still meet it there.

Section 03 · Availability

Which Objects and Editions Support Dynamic Forms?

Dynamic Forms works on custom objects and on most, but not all, standard objects that are enabled for Lightning Web Components (LWC). It is available in Group Essentials, Professional, Enterprise, Performance, Unlimited and Developer editions, in Lightning Experience and the Salesforce mobile app. Building pages needs the Customize Application permission.

  • The quick test: open the object's record page in Lightning App Builder. If the component panel has a Fields tab, the object supports Dynamic Forms. If it does not, it doesn't.
  • Not supported: objects that are not LWC-enabled, such as Products, Events and Tasks, which keep using the page layout. The Note object is also excluded because its layout is fixed.
  • Templates: Dynamic Forms doesn't work on pages built from custom templates.
  • Reference list: Salesforce keeps the list of LWC-enabled objects in LWC Migration for Record Home Pages.

Some record pages already have Dynamic Forms turned on by default. For an older org, expect a mix: newer pages built on field sections, older ones still on the Record Detail component. A short inventory of which pages use which is the first job of any migration.

Section 04 · Setup

How to Set Up Dynamic Forms: Step by Step

Open a record page in Lightning App Builder, select the Record Detail component and click Upgrade Now. The migration wizard asks which page layout to copy, then replaces Record Detail with field sections you can rearrange. You can also start from a blank page and drag Field Section and Field components onto it. Save, test, then activate.

The steps below use the example from our original guide: a custom Candidate object in a recruiting app, where HR needs confidential fields that hiring managers should not see.

  1. 1

    Open the record page in Lightning App Builder. From a record, choose Setup, then Edit Page. Or go to Object Manager, open the object, and select Lightning Record Pages. The first time you choose Edit Page, Salesforce makes a copy of the standard page for you to edit.

  2. 2

    Upgrade the Record Detail component. Click the Record Detail component, then Upgrade Now in the properties pane. Pick the page layout whose fields you want. The wizard brings over its fields, sections and save options, removes Record Detail, and adds field sections in its place.

  3. 3

    Arrange sections where users need them. Drag sections into tabs or accordions. In the example, a "Candidate Information" tab holds the everyday fields, and a separate "Confidential Information" section holds salary expectations and notes. Turn on Align fields horizontally for two-column sections.

  4. 4

    Set Required and Read-Only per page. Select a field and set its behavior in the property panel. This applies to this page only. Make sure every universally required field is on the page: they are not added automatically, and records cannot be saved without them.

  5. 5

    Add visibility rules. Give the "Confidential Information" section a filter on the user's profile equal to HR. Give a "Distance Willing to Travel" field a filter on the record's "Willing to Travel" checkbox, so it appears the moment the box is ticked.

  6. 6

    Decide how phone users will see it. If Dynamic Forms on Mobile is on, phone users see the same sections. If it is not, the wizard adds a Record Detail - Mobile component. On a page you built from scratch, you must add that component yourself.

  7. 7

    Check performance, save and activate. Click Analyze in the toolbar to see the page's performance score. Save, then activate the page as the org default or for specific apps, record types and profiles. Test as a user from each audience before rollout.

If you change your mind during a migration, the undo button rolls back the switch. If you later decide not to use Dynamic Forms on a page, remove its field sections and fields and add the Record Detail component back.

Section 05 · Visibility Rules

How Do Visibility Rules Work in Dynamic Forms?

A visibility rule is a filter on a field or section: when its conditions are met, the component appears, and until then it is hidden. Rules can test the record's fields, fields on related records, the user, the user's permissions and the device. Field rules update live while a user edits. Section rules are only evaluated after the record is saved.

That last difference catches most teams. In the recruiting example, "Distance Willing to Travel" appears as soon as the checkbox is ticked, because it is a field rule. If you had put the rule on a whole "Travel Details" section instead, the section would only appear after the user saves. Put rules that respond to editing on fields. Put rules that depend on who the user is, or the record's settled state, on sections.

Rules of thumb from the documentation

  • Hidden is not secure. Values in hidden fields still appear in reports, dashboards and list views. Salesforce describes hidden fields as a convenience, not field-level security.
  • Hidden edits are discarded. If a field is hidden by a rule when the user saves, any change to its value is not saved.
  • Required can be bypassed. A field made required in Lightning App Builder can be left blank if a rule hides it. A universally required field cannot, so never hide one.
  • No access means false. If a user can't see a field used in a rule's filter, the filter evaluates to false and the component stays hidden.
  • Lookups need values. A lookup used in a filter must always have a value. If it resolves to null at run time, the page won't load properly.
  • One value per filter. Filters take a single value, not a comma-separated list. Add a filter for each value and combine them with filter logic.
  • Five spans at most. A filter can reach through up to five relationship fields, such as Account, then Owner, then Manager.
  • Watch empty tabs. If every component in a tab is hidden, the tab disappears. If every section is inside a hidden tab, the create and edit windows are blank.

Salesforce also lists two exceptions: dependent picklists ignore visibility rules, and rules based on parent object fields are a known issue that does not work correctly. Test both before relying on them.

Section 06 · Mobile

Do Salesforce Dynamic Forms Work on Mobile?

Yes. Turn on "Dynamic Forms and Dynamic Highlights Panel on Mobile" in Salesforce Mobile App setup, and phone and tablet users of the Salesforce mobile app see the same sections and rules as desktop users. Then remove the Record Detail - Mobile component from each existing page, or mobile users keep seeing the old layout.

Our 2022 guide told you to add the Record Detail - Mobile component because field sections did not run on phones. That component still exists for orgs that have not enabled Dynamic Forms on Mobile. It wraps the page layout's fields in a mobile-only container, so desktop users see your field sections and phone users see the layout. Once the mobile setting is on, it becomes the thing standing in the way.

Org settingWhat phone users seeWhat to do
Dynamic Forms on Mobile offFields from the page layout, through Record Detail - Mobile. Field and section visibility rules are ignored.Keep Record Detail - Mobile on every page that supports phones. Add it yourself on pages built from scratch.
Dynamic Forms on Mobile onThe same field sections, fields and rules as desktopRemove Record Detail - Mobile from existing pages and confirm the page is activated for the phone form factor.

Mobile considerations before you switch

  • Offline: offline draft edits to record pages aren't supported with Dynamic Forms on Mobile, and record-home offline priming isn't supported either. Check this first if field teams work without signal.
  • Turning it off later can remove fields and sections from pages on mobile. Add Record Detail - Mobile back if you disable the setting.
  • Tablets: the Salesforce mobile app on a tablet uses the phone form factor, while a browser on a tablet uses desktop. Device-based rules behave differently in each.
  • Visualforce appears when viewing a record on mobile, but not when editing it.
Section 08 · Limits

What Are the Limits and Known Issues of Dynamic Forms?

The hard limits are 100 fields per column in a Field Section and 100 sections per region. The practical limits matter more: several Salesforce features still read the page layout, migrations drop some layout elements, and a few behaviors differ from Record Detail. Each limit below comes from Salesforce's limitations, tips and known issues pages.

1. Migration drops what doesn't fit. The wizard brings over the first 100 sections per region and 100 fields per column. The rest are dropped, even required fields. Custom links and blank spaces from the layout are not migrated, and some save options must be set again by hand.
2. Page layouts are still read elsewhere. Inline editing in list views, key fields in a path, the printable view, Clone with Related on opportunities and View All Dependencies all use the page layout, not the Dynamic Forms fields.
3. Don't mix Record Detail and field sections. Salesforce recommends against having both on one page. It can cause overlapping save bars and visibility rules that stop working.
4. Place each field only once. Two copies of a field with different rules, required settings or behavior can cause run-time problems, including with editing records.
5. Cross-object fields are read-only. Fields pulled through a lookup can't be edited on the page. Polymorphic lookups, such as a task's Who field (a contact or a lead), and User object fields aren't supported.
6. Managed package fields need a license. An admin without a license for a managed package doesn't see its fields in the builder, and saving the page removes them.
7. Columns count as components. A two-column Field Section counts as three components toward the page's component total.

The original version of this guide warned that complex rules can slow a page and that some field types may be unsupported. Both are fair, so here is how to handle them: keep visibility rules readable, and check field types against the visibility rule considerations before you design around them.

Section 09 · Performance

How Do You Keep a Dynamic Forms Page Fast?

Load less on first view. Put secondary sections and heavy related lists in tabs that aren't the default or in Accordion sections, so they load only when opened. Check the score with Analyze in Lightning App Builder, and track real load times in the Lightning Usage App. Dynamic Forms makes this easier, because fields no longer have to sit in one block.

  • Fields: Salesforce recommends fewer than 60 fields in a Record Detail component. On mobile, more than 25 detail fields or more than 5 related lists can cause performance issues.
  • Phones: aim for at most eight visible components per page. Move the rest into tabs or accordions, or hide them for phones with a device filter.
  • Analysis: Performance Analysis for App Builder runs as you build and offers suggestions. Components in tabs that aren't the default, and in accordions, are not included in the analysis.
  • Measure: Salesforce measures load time as Experienced Page Time (EPT). The Lightning Usage App shows your most-used pages and their load times by browser and page.
  • Custom code: the programmatic accordion components (lightning-accordion) don't lazy load like the App Builder Accordion does.

The tabbed layout from the setup example helps here too. Everyday fields load first, and the confidential section and related lists load only when an HR user opens them.

Section 10 · Checklist

A Dynamic Forms Migration Checklist

The wizard converts one page in minutes. Migrating an org takes longer, because the decisions behind each page are the real work. This is the sequence we follow, built from the limits above.

StepWhat to do
1. InventoryList each object's Lightning record pages, page layouts, record types and assignments. Note which pages already use field sections.
2. ConsolidateFind layouts that exist only to show or hide a few fields. These are the candidates to replace with one page and visibility rules.
3. Design rulesWrite each visibility rule in plain language before you build it. Decide field rules versus section rules using the save-time behavior.
4. Separate securityAnything confidential gets field-level security as well as a visibility rule. Hiding is not protection.
5. Build in a sandboxMigrate there first. Check that the wizard kept every field, add back custom links and save options it dropped, and add all universally required fields.
6. Test by personaCreate, edit and clone as each profile, record type and device. Include list view edits, paths and quick actions, which may still use the layout.
7. Plan mobileDecide on Dynamic Forms on Mobile, confirm offline needs, and remove or keep Record Detail - Mobile to match.
8. Roll out and keep layouts tidyActivate by app, record type and profile, tell users what changed, and keep page layouts current for the features that still read them.

A record page only pays off if people use it. Our guide to CRM adoption after implementation covers the rollout side of a change like this.

Section 11 · How We Help

How Twopir Consulting Helps With Dynamic Forms

Twopir Consulting is a Salesforce Partner and HubSpot Partner. We help growing and mid-market companies solve complex CRM, integration and business system challenges: we implement, rescue, optimize, and integrate complex CRM and revenue systems. For record pages, that means turning layouts that grew without a plan into pages each team can work in, without losing data or breaking the processes that still rely on layouts.

Ready to Start

Plan Your Move From Page Layouts to Dynamic Forms

On a 30-minute discovery call, a Twopir Salesforce architect will look at your objects, layouts and record types, and tell you which pages to migrate first and what to watch for.

Schedule a Discovery Call
Section 12 · Bottom Line

The Bottom Line

Dynamic Forms is the most flexible way to build Lightning record pages on supported objects. It replaces layout sprawl with one page per audience, places fields where users work, and shows each field only when it is relevant. It works best when you treat visibility rules as design, not security, plan mobile from the start, and keep page layouts current for the features that still read them.

  1. 1

    Dynamic Forms moves fields from the page layout onto the Lightning page as Field and Field Section components.

  2. 2

    It supports custom objects and most LWC-enabled standard objects. If you see a Fields tab, the object supports it.

  3. 3

    Field rules react while users edit; section rules only after save. Hidden fields are not secured.

  4. 4

    Enable Dynamic Forms on Mobile and remove Record Detail - Mobile, or phone users keep the old layout.

  5. 5

    Migrate in a sandbox and test as each persona, including list views, paths and quick actions.


FAQ

Frequently Asked Questions

Dynamic Forms is a Lightning App Builder feature that replaces the single Record Detail component with separate Field and Field Section components. Admins place them anywhere on a Lightning record page and show or hide each one with visibility rules based on record data, the user, permissions or device, without code.

Yes, on most standard objects that are enabled for Lightning Web Components, as well as custom objects. Objects that are not LWC-enabled, such as Products, Events and Tasks, still use page layouts, and the Note object is not supported. If the Fields tab appears in Lightning App Builder, the object supports Dynamic Forms.

Salesforce lists Dynamic Forms in Group Essentials, Professional, Enterprise, Performance, Unlimited and Developer editions, in Lightning Experience and the Salesforce mobile app. Creating and saving Lightning pages in Lightning App Builder needs the Customize Application permission.

No. A visibility rule only hides a field on that Lightning page. The value stays visible in reports, dashboards and list views, and Salesforce describes hidden fields as a user convenience, not field-level security. Use field-level security and permission sets to control who can read or edit sensitive data.

Visibility rules on Field Section components are evaluated only after the record is saved. Rules on individual Field components are evaluated live, as the user edits. If a section should appear as soon as a user changes a value, put the rule on the fields inside it instead.

In Setup, open Salesforce Mobile App and enable Dynamic Forms and Dynamic Highlights Panel on Mobile. Then edit each existing Dynamic Forms page, remove the Record Detail - Mobile component and confirm the page is activated for phones. Without that removal, mobile users still see only the page layout fields.

Yes. Inline editing in list views, path key fields, the printable view, Clone with Related on opportunities and objects that are not LWC-enabled still read the page layout. Dynamic Forms can reduce how many layouts and record types you need, but keep the remaining layouts accurate.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting works with growing, mid-market, and enterprise organizations that need help with complex CRM implementations, integrations, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems on Salesforce and HubSpot, for clients across the US, UK, Australia and New Zealand, the UAE and Canada.