Dynamic Forms Tips and Considerations
Keep these tips and considerations in mind when working with Dynamic Forms.
Required Editions
| Available in: Lightning Experience |
Available in: Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
General Considerations
- Lightning App Builder preview respects density settings for field sections with one exception. If you have the Compact density setting enabled, you don't see the field labels and field values aligned on the same row on the Lightning App Builder canvas.
- When you switch page templates on a page that uses Dynamic Forms, the list of available templates contains only the templates that are supported for your Dynamic Forms-enabled page.
- Some fields get special handling in Dynamic Forms. They're set to Read-Only or Required and that state isn’t editable in the properties panel.
- If you add more than one instance of the same field to a Lightning page, all instances of that field on the page show the same data. However, two or more instances of the same field on a page with different visibility rules, UI behavior, or requiredness settings can cause problems with the page at run time, including issues with record edit behavior.
- Programmatic versions of the accordion components don’t provide the same functionality
as their App Builder counterparts. For example,
lightning-accordionandlightning:accordioncomponents don’t currently support lazy loading. - Expanding or collapsing a field section while designing a page has no effect on whether a section is expanded or collapsed for users during runtime.
- When you save a new custom object record with an empty object name, the API populates the custom object name field with the record ID. Make sure that the Name field is on the page and is marked as required.
- When Dynamic Forms-enabled pages display on a tablet, field sections inside tabs have more left padding than field sections outside of tabs.
- When adding new custom fields to Dynamic Forms-enabled Lightning pages as part of field creation, fields are added as the last field in the first column on the first field section on the page in top-down, left-to-right order. If the field section is in a container, such as a Tabs or Accordion component, then the first field section is chosen from the first tab or the first accordion section. The “active” tab doesn’t matter. If the first field section on a page is the Dynamic Highlights Panel, then new fields are added to the second field section instead.
- When you view a Dynamic Forms-enabled record page on a mobile device, tapping the address field results in different behavior depending on whether Dynamic Forms on Mobile is enabled in your org. When Dynamic Forms on Mobile isn’t enabled, tapping an address field opens a prompt to select a map app. When Dynamic Forms on Mobile is enabled, tapping an address field takes you immediately to Google Maps™.
- When you create a record from a Dynamic Forms-enabled record page, the success confirmation toast message doesn't include a link like it does when you create a record from standard record pages.
- When you click a compound address field from a Record Detail component, it opens in Google Maps™ with just the address populated. When you click a compound address field from a Dynamic Forms-enabled page, it opens in Google Maps showing both the address and the latitude and longitude values. However, if the latitude and longitude values point to an area with no known address, Google Maps doesn't show an address.
- The User Interface setting Enable Collapsible Sections doesn't apply to Lightning record pages when Dynamic Forms is enabled on the page. This setting applies only to record pages in Salesforce Classic and to Lightning record pages that use the Record Detail component. The Dynamic Forms expand and collapse functionality takes precedence over the Enable Collapsible Sections setting.
General Tips
- We recommend not having both a Record Detail component and field sections on the same
page. If you do, users can have issues with the page, including:
- Multiple, overlapping save and cancel bars when both are on the page and both in inline edit.
- Visibility rules on Field and Field Section components not working properly.
- When users create, edit, or clone a record that uses Dynamic Forms, the fields they see come from the field sections on the page, not from the Record Detail component.
- Field sections are top-down-left-right tab order only, while Record Detail is left-right-top-down tab order, which can cause confusion. As a result, fields inside a Field Section sometimes don’t line up horizontally, while Record Detail fields do. If you want the fields to retain their horizontal alignment inside a field section, select the Align fields horizontally checkbox.
- Dynamic actions are supported on custom objects. Actions on standard objects come from the record details on the page layout, not from the Dynamic Forms fields on the page.
Mobile Tips
Note Dynamic Forms on Mobile gives your mobile users the same experience that your desktop
users have. To avoid these mobile considerations, from Salesforce Mobile App Setup, enable
Dynamic Forms on Mobile.
- Don’t place Field Section components on mobile-only Lightning pages. Field Section components are desktop-only and don’t appear when the page is viewed on a phone.
- You can use one Lightning page for both desktop and phone. Add the Record Detail - Mobile component to the same page with your Field Section components. Your desktop users see the Field Section component, and your mobile users see the Record Detail - Mobile component.
Visibility Rules and Dynamic Forms
- Field and Field Section components are supported on desktop only. Therefore, the visibility rules that you set on them are respected only in the desktop view, not on mobile. However, Dynamic Forms on Mobile gives your mobile users the same experience that your desktop users have. To avoid this issue, from Salesforce Mobile App Setup, enable Dynamic Forms and Dynamic Highlights on Mobile.
- If a field is hidden on a page due to a visibility rule, and a user edits the value of the field, its new or changed value isn’t saved.
- Dependent picklist fields don’t respect visibility rules. Even if they have visibility rules assigned to them, dependent picklist fields still appear in the View All Dependencies list.
- Component visibility rules on field sections behave differently than they do on fields. Visibility rules on fields are assessed dynamically. Changes a user makes while editing a record can make fields appear and disappear as visibility rules are evaluated. Visibility rules on field sections aren’t dynamic and don’t react to what a user does while editing. Field section visibility rules are evaluated only after the record is saved.
- If you hide a field with a visibility rule, users don’t lose access to the field’s data. Values in hidden fields remain intact and are visible outside of the Dynamic Forms-based page in places like reports, dashboards, and list views. Hidden fields are for user convenience, not for field-level security.
- When a tab is hidden by a visibility rule, any field sections within that tab are hidden in the Create and Edit windows. If all field sections on a page are contained in the hidden tab, then the Create and Edit windows are blank.
Did this article solve your issue?
Let us know so we can improve!
