Dynamic Forms migration and limitations
Key Takeaway
Dynamic Forms puts fields on the Lightning record page, but some features still read the page layout. These include "Clone with Related" for opportunities and inline editing in list views, so keep the fields they need on the page layout.
Dynamic Forms turns a page layout's fields and sections into separate Field and Field Section components in the Lightning App Builder. You can place these components anywhere on a Lightning record page and show or hide them based on conditions, without managing a separate page layout. To move an existing page to Dynamic Forms, you use the migration wizard. The wizard has limits on what it carries over, and the page layout still applies in some places. Knowing both tells you what to check after you migrate.
What Dynamic Forms changes
Dynamic Forms moves fields and sections out of the single Record Detail component and into individual Field and Field Section components. You can spread these components across columns and tabs.
You can show or hide Field and Field Section components with visibility rules. You assign only the Lightning record page, instead of assigning both a Lightning record page and a page layout. Visibility rules can also reduce the number of page layouts and record types you need.