Keep these limits and limitations in mind when working with Lightning pages and Lightning apps in the Lightning App Builder.
Required Editions
| Lightning App Builder available in: both Salesforce Classic and Lightning Experience |
| Lightning Home and utility bar pages available in: Lightning Experience |
| Lightning app and record pages available in: both the Salesforce mobile app and Lightning Experience |
| Email application pane pages available in: both Salesforce Classic and Lightning Experience |
|
Available in: Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
- In Salesforce Classic, the Default On and Default Off options for Lightning page tabs don’t work the same way as for other custom tabs. The Lightning page menu item appears for the selected profiles in Salesforce for Android, Salesforce for iOS, and Salesforce mobile web whether you choose Default On or Default Off. To hide the Lightning page for the selected profiles, select the Tab Hidden option.
- You can place up to 100 tabs in a Tabs component.
- A Lightning page region can contain up to 100 components.
- The columns inside a Field Section are considered components. A Field Section component with two columns counts as three components when determining the total components on a page.
- Each tab in a Tabs component and each section inside an Accordion component counts against the limit for total components on a page. For example, a Tabs component containing three tabs counts as four components.
- Lightning component global actions aren’t supported for app pages.
- Page overrides by profile aren’t supported in packaging. They’re supported in change sets, but must be added manually.
- Dropdown menus in the Lightning App Builder can display up to 200 items. Enter a few characters, and all available matches are displayed as you type.
- Although you can add the Potential Duplicates component to person account pages, the component doesn’t display duplicate person accounts.
- Custom tab labels in the Tabs component—including those labels installed from
packages—aren’t translated. For example, if you create a custom Goals tab in English, then
view the page as a user whose language is set to French, the tab still displays as Goals.
However, you can use the
{!$Label.customLabelName}expression in a component label or attribute to represent a custom label that you create in Setup by using the custom label feature. For more information, see “Build Localized Component Labels and Attribute Values on Lightning Pages with Custom Labels.” - Right-to-left (RTL) language layout isn't supported in the Lightning App Builder.