Hi Friends today we are going to discuss here Dynamic Forms Limitations
General
- Dynamic Forms is supported for most, but not all standard LWC-enabled objects. See LWC Migration for Record Home Pages for a list of LWC-enabled objects. If you open a record page for an object in the Lightning App Builder and don't see a Fields tab in the component panel, then Dynamic Forms isn't supported for that object. As an example, the Note object doesn’t support Dynamic Forms because it has a fixed layout.
- Dynamic Forms isn’t supported on objects that are not LWC-enabled. For example, Campaigns, Products, and Tasks, which are not LWC-enabled, use information from page layout.
- Dynamic Forms doesn’t work in Internet Explorer 11. Users with IE 11 who try to view a page that uses Dynamic Forms get a page error.
- Dynamic Forms doesn’t work on pages based on pinned region templates and custom templates.
- Blank spaces aren’t supported.
- You can add up to 100 fields per column in a Field Section component.
- If you convert a section from two columns to one, the new single column can only hold 100 fields. If you had more than 100 fields total between the two columns, when you switch to a single column, the first 100 fields are moved into the single column, and the rest of the fields are dropped. If you change your mind after switching to single column, you can revert the change by immediately clicking the undo button (
). - Users can expand or collapse field sections only while in view or inline edit mode, not in the full edit, create, or clone windows. If you expand or collapse a field section and then refresh your browser, including pulling to refresh, the expanded or collapsed state doesn’t persist.
- If you have Opportunity Products enabled and have the Prompt users to add products to opportunities setting enabled, when you create an opportunity from either an opportunity-related list or from opportunity home, the create window uses record details from the page layout.
- The Clone with Related action for opportunities uses record details from the page layout even if the opportunity page you launch the action from uses Dynamic Forms.
- When viewing an external or non-UI API-supported object record that has a related list for a child object that supports Dynamic Forms, if you create a record for that child object from the parent record related list, the create window uses record details from the child object page layout.
- When configuring key fields in a path, the fields in the Available Fields list come from the record details on the object’s page layout, even if the page the path resides on uses Dynamic Forms.
- The Lightning App Builder Record Detail to Dynamic Forms migration tool doesn’t migrate all possible layout save options. For example, when saving a layout, if Default is checked but Show on edit page is unchecked, then this option isn’t migrated. Manually set this value after migration.
- The fields available for inline editing in list views are determined by the fields on the page layout, not the ones configured with Dynamic Forms.
Migration
- Only fields, sections containing fields, and layout save options are included when migrating a page to Dynamic Forms. Other elements on the page layout, such as custom links and blank spaces, aren't included.
- You can add up to 100 fields per column in a Field Section component. And you can add up to 100 sections per region. As a result, if you use the migration tool to import fields and sections from a page layout that has more than those limits, then we migrate up to the first 100 sections in each region and the first 100 fields in each column. The rest of the fields are dropped, even if they’re required fields. You can manually add the dropped items later. If you change your mind after you make the switch, you can click the undo button () to roll back the changes.
- The Lightning App Builder Record Detail to Dynamic Forms migration tool doesn’t migrate all possible layout save options. For example, when saving a layout, if Default is checked but Show on edit page is unchecked, then this option isn’t migrated. Manually set this value after migration.
Reference Link:-
