Overview
- Salesforce Dynamic Forms let Admins place individual fields on a Lightning Record Page instead of one fixed Page Layout.
- They reduce duplicate Page Layouts and Record Types by showing different fields to different teams.
- They run inside Lightning App Builder and are fully supported on the Salesforce Mobile App.
- They do not replace Page Layouts — most Salesforce orgs use both together for the best results.
Salesforce Dynamic Forms let Salesforce Admins build Lightning Record Pages field by field, instead of relying on one fixed Page Layout for every user. Admins can place individual fields and field sections exactly where they belong and set simple rules for when each appears, so people see only the information that matters to them, without a pile of extra Page Layouts and Record Types behind the scenes. This guide covers how Salesforce Dynamic Forms work, where they fit alongside Lightning App Builder and the Salesforce Mobile App, and how to start using them safely.
What Are Dynamic Forms in Salesforce?
Dynamic forms in Salesforce are a feature inside Lightning App Builder that separates individual fields and field sections from the standard Record Detail component. Before this feature existed, every field on a record page came from one Page Layout, shared by everyone assigned to it. If two teams needed to see different information on the same object, an Admin usually had to build a second Page Layout and Record Type, then keep both in sync as the business changed.
With Salesforce Dynamic Forms, fields become components an Admin can drag onto a Lightning Record Page one at a time, each carrying its own visibility rule. Different users can then see a different version of the same record without a second Page Layout, which is the core idea behind dynamic forms Salesforce teams now use to cut down on layout sprawl.
It is also one of the more common requests our Customization Services team handles for clients whose Record Pages have outgrown a single layout. If you are still deciding which Salesforce products your org actually needs before investing time in page design, our guide to the different Salesforce Clouds is a useful starting point.
How Do Salesforce Dynamic Forms Work Inside Lightning App Builder?
Everything happens inside Lightning App Builder, the same tool used to design any Lightning Record Page. Add a Field Section component and drag fields onto it the way you would drag any other component. Each field can be marked read-only or required, and given a filter that controls when it shows up, based on the record’s own values, the user’s profile, or other simple conditions.
Field sections behave a little differently from single fields, and this catches a lot of new Admins out. A field becomes visible or hidden immediately as someone edits a record, while a field section only updates once that record is saved. Test both types of visibility rules on a sandbox page before rolling anything out to real users.
Dynamic Forms only works on objects that support Lightning Web Component record pages. A handful of standard objects, including Campaigns and Tasks, still rely entirely on Page Layouts, so check object support before planning a migration.
Why Salesforce Admins Are Switching to Salesforce Dynamic Forms
Dynamic Forms is not just a new way to arrange fields; it changes how much ongoing maintenance a Record Page needs, which is often where our Consulting Services team gets involved early, before a page design decision becomes hard to unwind.
- Fewer Page Layouts and Record Types, since one Record Page can show different fields to different teams.
- Cleaner, less crowded records, because fields that only matter to one team stay hidden from everyone else.
- Faster page loads, since fields grouped in Tabs or an Accordion only load when a user opens them.
- Simpler handoffs, as a new Admin can adjust one field section instead of an entire Page Layout.
Dynamic Forms on the Salesforce Mobile App
Dynamic Forms is fully supported on the Salesforce Mobile App, on both iOS and Android, so users get the same field-by-field layout and visibility rules whether they are at a desk or out in the field. To turn it on, go to Setup, search for the Salesforce Mobile App page, and switch on Dynamic Forms there.
If a Record Page was already using the standard Record Detail component on mobile before this was switched on, that component needs to be removed and replaced, otherwise mobile users keep seeing the old layout instead of the new one. Testing on an actual phone, not just the desktop preview, is the only reliable way to confirm a page is genuinely ready.
Dynamic Forms vs Page Layouts: Which One Do You Need?
Page Layouts are not going away, and Dynamic Forms is not a full replacement for them. Page Layouts still control related lists, buttons, and quick actions, along with any object Dynamic Forms does not yet support.
Dynamic Forms earns its place when a Record Page needs to look different for different people, has grown too crowded, or needs a section of fields to appear only under specific conditions. For a simple object with one audience, a standard Page Layout is often still the fastest option. Most orgs end up using both together: Page Layouts where Salesforce still depends on them, and Dynamic Forms where finer control pays off. If you are not sure which Record Pages in your org would benefit most, a Health Check Services is a straightforward way to find out before committing time to a redesign.
Getting Started With Dynamic Forms
Open a Lightning Record Page in Lightning App Builder and select the Record Detail component for an upgrade option, or start from scratch. Add a Field Section, drag in the fields users actually need, and apply visibility rules only where they add value, since too many conditions become hard to troubleshoot.
Once the layout looks right, turn on mobile support and check it on a real phone before rolling it out. If a full migration feels risky on a heavily used object, start small: pick one Record Page, get it right, then use it as the template for the rest of the org. For larger rollouts across many objects, our Implementation Services team can plan and sequence the migration so nothing breaks along the way.
Final Thoughts
Getting the visibility rules and object support right the first time saves a lot of rework later, especially on Record Pages used by hundreds of people every day. TechForce Services is a Salesforce Summit Partner, and our certified Salesforce Admins have migrated Record Pages for enterprise teams across Australia, the US, and the UK, with our Managed Services for Salesforce team keeping them running smoothly afterward. If your org is planning a move to Salesforce Dynamic Forms, or wants a second opinion on an existing setup, our team is ready to help.
FAQ
What is Salesforce Dynamic Forms?
Salesforce Dynamic Forms is a Lightning App Builder feature that lets Admins place individual fields and field sections directly on a Lightning Record Page, with rules controlling when each one is visible to a given user.
How do I enable Dynamic Forms in Salesforce?
Open the Lightning Record Page in Lightning App Builder, select the Record Detail component, and choose Upgrade Now. For mobile, switch on Dynamic Forms separately from the Salesforce Mobile App setup page.
Does Dynamic Forms work on every object?
No. It only works on objects that support Lightning Web Component record pages. Some standard objects, such as Campaigns and Tasks, still rely on Page Layouts only.
Do Dynamic Forms replace Page Layouts?
No. Page Layouts still manage related lists, actions, and any object Dynamic Forms does not support. Most orgs run both side by side.
What are the main benefits of Dynamic Forms for Salesforce Admins?
Fewer duplicate Page Layouts, cleaner records for end users, faster-loading pages, and the ability to give different teams a different view of the same record without extra setup.
Is Dynamic Forms available on the Salesforce Mobile App?
Yes, on both iOS and Android, once it has been switched on from the Mobile App settings inside Setup.
