Salesforce Dynamic Forms change how admins build record pages in Lightning. Instead of relying only on a traditional page layout, admins can place fields and field sections directly on the Lightning record page, then control when they appear based on record data, user details, profile, or device.
The practical benefit is flexibility. A sales rep, support agent, manager, and admin do not always need to see the same fields in the same order. With Dynamic Forms, the record page can adapt to the user and the context of the record, rather than forcing everyone into one fixed layout. Dynamic Forms are especially useful when a page has too many fields, too many conditional sections, or too many teams using the same object in different ways. Instead of creating more page layouts and record type combinations, admins can build a cleaner Lightning page with conditional visibility rules.
This guide explains how Salesforce Dynamic Forms work, when to use them, how to set them up, what changes on mobile, and which limitations to plan for before rolling them out across your org.
What Are Salesforce Dynamic Forms?
Salesforce Dynamic Forms are a Lightning App Builder feature that lets admins add fields and field sections directly to a Lightning record page. Each field becomes part of the page configuration, rather than being controlled only by the traditional page layout in Setup.
In a traditional Salesforce page layout, fields are arranged in one central layout and assigned based on profile and record type. That model works, but it can become difficult to manage when different teams need different views of the same object.
Dynamic Forms move that control to the Lightning record page. Admins can create modular field sections, drag them into different parts of the page, and apply visibility rules to show or hide fields based on conditions.
For example, you might show renewal fields only when an Opportunity is in a renewal stage. You might show escalation details only when a Case priority is high. You might show finance-related fields only to users in a finance profile or permission set.
In simple terms: traditional page layouts control the general structure of a record page; Dynamic Forms let the page respond to the record and the user.
Prerequisites and Permissions
Before enabling Dynamic Forms on a record page, confirm a few things are in place. Skipping this step is the most common reason teams get stuck partway through setup.
- Lightning Experience enabled. Dynamic Forms are a Lightning-only feature. Classic users will not see the new layout.
- The right edition. Dynamic Forms are available on Enterprise, Performance, Unlimited, and Developer editions, plus Professional Edition with the Lightning App Builder add-on.
- Admin-level permissions. The user configuring Dynamic Forms needs Customize Application or equivalent permissions to modify Lightning record pages.
- A backup of the existing layout. Once you migrate a record page to Dynamic Forms, the original page layout no longer controls field placement on that page. It is good practice to clone or export the layout before migrating, in case you need to roll back.
- A test profile or sandbox. Dynamic Forms behave differently for different users depending on visibility rules. Validating in a sandbox or with a test profile prevents surprises in production.
Accessing and Activating Dynamic Forms
Dynamic Forms can be conveniently accessed from the object record itself. Simply navigate to "Edit Page" or directly from the Lightning record page of the relevant object.
If the functionality is not yet enabled, you'll be presented with an "Upgrade Now" button to initiate the process.
Populating Your Field Sections
After incorporating a "Field Section" component onto your page, you can begin adding individual fields. Unlike traditional layouts, these sections can be placed virtually anywhere, offering greater layout flexibility.
Start with Core Fields
Begin by including fields that should be universally visible to all record viewers. Remember to assign a descriptive name to each field section for clarity.
Tailoring Field Behavior
Once a field is selected, you can customize its behavior by defining options like "Read Only" or "Required," ensuring data is collected effectively.
Dynamic Visibility
Control the visibility of both individual fields and entire field sections based on specific criteria.
Cross-Object Fields
Dynamic Forms in Lightning App Builder unlock the power of lookup relationships. Drag cross-object fields from the component palette directly onto your record page. This eliminates the need to switch tabs and centralizes relevant data from linked objects, offering a more comprehensive view in a single location.
Strategic Whitespace
Whitespace separates visual elements, preventing them from competing for attention. This creates a clear hierarchy, guiding the viewer's eye towards the most important information.
Streamlined Field Creation
Dynamic forms allow adding new fields directly during creation, eliminating separate steps and saving you time. This in-line approach fosters adaptability for your evolving data needs.
Record Detail - Mobile Component
From the Salesforce Mobile App Setup, enable “Dynamic Forms on Mobile”.
- Desktop Optimization: When users access the page on a desktop computer, they see the standard field sections you've configured, providing a clear and organized layout.
- Seamless Mobile Experience: For mobile users, the Record Detail - Mobile component automatically takes over. It presents a streamlined and optimized view of the essential fields, catering to the limitations of smaller screens.
This approach ensures a responsive design, automatically adapting the field layout to match the user's device. By leveraging this feature, you can guarantee a consistent and user-friendly experience for everyone interacting with your record pages.
Best Practices for Effective Implementation
- Single Layout Efficiency: Aim for a single, well-organized layout per object for optimal management.
- Conditional Visibility & Access: Leverage the power of conditional logic to control field visibility (including read-only and required) based on specific criteria.
- Sectional Visibility and Management: Group related fields within sections and manage their visibility as a whole. This simplifies administration, especially for scenarios where certain departments don't require access to extensive field sets.
- Granular Permission Control: Establish field-level permissions as needed to comply with client requirements. For a wider view on permissions and access, see our guide on Salesforce data security best practices.
- Dynamic Field Visibility: Utilize dynamic field visibility based on other field values, similar to Flow functionality, for a truly responsive data collection experience.
Common Errors and Limitations
Most Dynamic Forms problems fall into a small set of recurring issues. Knowing them up front saves time during rollout.
Page becomes slow with many fields. Each field section and visibility rule adds rendering overhead. Pages with 100+ fields or dozens of conditional rules can feel sluggish, especially on slower connections. Split heavy pages into tabs, or move rarely used fields into a collapsible section.
Visibility rules do not behave as expected. Filters in Dynamic Forms use Lightning record page filter logic, not Flow logic. Multi-condition rules with AND/OR need parentheses to behave correctly. If a field is appearing or hiding incorrectly, the rule is almost always the issue, not the data.
Some standard components are not supported. A few standard Salesforce components and managed package components do not work alongside Dynamic Forms. If a component disappears after migration, check whether it is supported on Dynamic Forms record pages.
Mobile experience differs from desktop. Even with “Dynamic Forms on Mobile” enabled, the rendering on small screens is more limited. Always test the mobile view separately, especially if your team uses the Salesforce mobile app heavily.
Migration is one-directional in practice. Once a record page is upgraded to Dynamic Forms, the original page layout no longer controls field placement on that page. Reverting means rebuilding, so clone the page before migrating.
Troubleshooting Resources
Should you encounter any unexpected behavior, remember to consult the official Salesforce documentation for limitations and known issues:
Key Takeaways
Salesforce Dynamic Forms move field and section configuration into the Lightning App Builder. This gives admins more control over how record pages look and when fields appear. The biggest benefit is conditional visibility. Dynamic Forms help reduce clutter by showing users the fields they need based on the record, user, or device. Dynamic Forms are most useful for objects with complex layouts, multiple teams, stage-based processes, or too many fields on the page. They do not replace field-level security, validation rules, or proper data governance. They improve the page experience, but security and data quality still need to be managed separately. The main risks are slow pages, overly complex visibility rules, unsupported components, mobile layout issues, and difficult rollback after migration.
Before enabling Dynamic Forms in production, back up the existing layout, test in a sandbox, validate with real users, and simplify the page instead of copying old clutter into a new format.
.png)
.png)
