What Are Salesforce Dynamic Forms?
Dynamic Forms
are created when we develop sensible, user-centric page layouts that expose the necessary details at the right moment.
The "Details" area or the page layout in Lightning pages might grow clogged with fields over time. These fields may be necessary, but not for all users or at all times.
The closest options for creating alternative page layouts and distinct profiles are configuration-intensive and labor-intensive.
How do Salesforce Dynamic Forms Work?
'Field Section,' a brand-new standard Lightning Component, is now available with Dynamic Forms. Simply add the component to the page, choose the fields to be included to the section, and create a filter to define:
- when to display the section,
- on the form factor to show it in, and
- whom to show it to
How do we set up Salesforce Dynamic Forms?
1. Create or migrate a page
- You must first access the Lightning page for which you wish to update any custom object. Next, choose "Upgrade Now" for the "Highlights Panel" or "Record Detail" component.
- You may also create a new page by jumping onto your custom object, selecting "Lightning Record Pages," and then selecting "New."
- After you build or migrate a new Lightning record page, you will see an opportunity to add a "Field Section" component that will allow you to directly attach fields to the Lightning record page.
2. Add fields to a component
After you've added a "Field Section" component to your page, you may add individual fields. A "Field Section" can be added in a variety of places other than tabs.
Let's start by adding certain fields that should be available to everyone who looks at the record:
- Remember to give each field area a name.
- You may specify the UI behavior for a certain field, such as "Required" or "Read Only."
3. Make fields and components conditionally visible
We?can?make?both?fields?and?all?field?components?visible.
The Field Section and Field visibility behave differently. Both, however, are dynamic, and when users make changes, the fields appear to be highly dynamic. It specifies that a field has the ability to appear or disappear when the user edits the record.
Field Sections, on the other hand, are only updated on Save, thus a new section appears or vanishes when the user saves the record.
They are elected when we pick accordions or tabs. So, even if you add numerous "Field Section" components to the opening page, you may use the accordion or tabs to improve efficiency and load.
5. Add a mobile component
If you want mobile visitors to look at the "Details" fields, you must include a component called "Record Detail – Mobile" to any pages you create. It's because the new "Field Section" component does not exist on mobile. This component will be immediately added to any transferred pages.
We may begin utilizing Dynamic Forms in two ways:
- Create a custom object record page, then add Field and Field components to it.
- Alternatively, open a current record page and use a migration wizard to migrate its record details.
A Quick Guide to Getting Started with Dynamic Forms in Salesforce
Let's get started with Dynamic Forms in Salesforce. This guide will cover everything.
- Activate Dynamic Forms
- Add Lightning Record Page Field Section Component
- Make a Filter to Control Component Visibility.
- Dynamic Forms must be tested.
What Are the Benefits of Dynamic Forms?
- Despite assigning a page layout and a Lightning page individually, the Lightning page is assigned using a single assignment mechanism.
- It reduces or simplifies page layouts by converting visibility rules into components rather than the full layout.
- Without utilizing the page layout editor, you may manage the sections and fields on your pages in the Lightning App Builder.
- Dynamic Forms has an intriguing visual interface that allows us to verify the fields that the end-user need.
- To enhance page load speeds, Dynamic Forms attach the sections and fields to the appropriate tabs or components.
- Rapid advancement from page layouts: Sections and fields can be placed wherever you desire.
- With component visibility rules, you may reduce the number of page layouts you desire.
- Profit from a single assignment model for the Lightning page, regardless of whether you're assigning a page layout or a Lightning page.
Limitations of Salesforce Dynamic Forms
- It does not allow for blank spaces, and the Traditional Page Layouts will always govern pertinent listings.
- It does not work on record pages with custom page templates or pinned areas.
- Because the new Field section and field components are not mobile device friendly, you must create a new Record-detail – Mobile Component.
- A field section component can have up to 100 fields/columns appended to it.
- At the moment, only custom objects support dynamic forms.
- Internet Explorer 11 does not support Dynamic Forms. Users of Internet Explorer 11 who attempt to browse a page that employs Dynamic Forms may get an error.
- It does not accept blank spaces.
- When transferring a page to Dynamic Forms, only fields and sections containing fields are encapsulated. The page layout excludes components such as blank spaces and custom links.
- If you transform two columns into one in a section, the resultant column can accommodate 100 fields. If you have more than that in two columns and switch to one column, the first 100 fields will be moved to a single column and the remaining fields will be dropped. If you change your mind after converting, you may immediately click the undo button, which is the Lightning App Builder Undo button.
- Dynamic Forms is only supported on record pages for custom objects.
- Dynamic Forms does not work effectively on sites that use custom or pinned region templates.
- A Field Section component can include up to 100 fields/columns.
- Allow migrating up to 100 sections in each area and the first 100 fields in each column if the page layout you want to migrate contains more parts and fields than we can handle. Even if the remaining fields are required, they are removed. You can manually add dropped items afterward. If you change your mind after switching, you may undo the changes by tapping the undo button, which is the Lightning App Builder Undo button.
- Field sections can only be collapsed or expanded in inline edit or view mode, not in the create, full edit, or clone windows.
Dynamic Forms Known Issues
- If you press View All Dependencies from the Path component, the dependencies you see are from the record, not from the Dynamics Forms fields on the page.
- At runtime, the CurrencyISOCode field is not shown. However, it continues to behave as expected.
- Many instances of the same lookup field on a Dynamic Forms-based page result in a page error that looks up an object that isn't supported by the UI API.
- When you tap New from the related list for a non-UI, API supported item that is holding a Forms-enabled object, the parent lookup field does not show in the New dialogue. You may still save the new record.
- Dynamic Forms field components are not supported by the Macro Builder. When a Dynamic Forms-enabled record is opened in the Macro Builder, the field components remain hidden.
- Density options are not admired in the Lightning App Builder preview for field sections, and the Comfy setting is always displayed in the Lightning App Builder preview for field sections. Proper density settings are applied during runtime.
- If you construct a record from a lookup, the fields that display in the window are not from the Dynamic Forms fields on the page, but rather from the record details. When you hover over the fields in the palette, the displayed data types are incorrect.
- The fields in two-column Field Section components do not line appropriately horizontally.
- A printed view of the record is determined by the fields on the default page rather than the fields on the Dynamic Forms-based page.
