Export and Packaging Considerations for Lightning Bolt Solutions
Before you export and package a Lightning Bolt Solution, keep the following considerations and limitations in mind.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
Tip We recommend using managed packages to avoid naming conflicts with other
packages in your customer’s org or your own.
Add Custom Apps
- When you include apps in a Lightning Bolt Solution, follow general guidelines in the Components in Managed Packages for developing and distributing Lightning apps.
- When you package the solution, app components are automatically added to the package. For example, the package includes customized fields, page layouts, and relationships with standard objects.
Add Flows
- To reuse a single flow or a group of flows, add them to a flow category. Then include the flow category in your Lightning Bolt Solution.
- You can add only active flows to a flow category.
Export and Package an Experience Builder Template
- An exported template name must be unique.
- You can export a customized template from Experience Builder and include it in a Lightning Bolt Solution, but including a template isn’t required.
- When you export a template from Experience Builder, the system removes non-alphanumeric characters from template and page names. For example, My Template #2 becomes My_Template_2.
- For navigation menu items that link to objects, list views are reset to the default list view. Also, custom list views for standard objects aren’t included as dependencies, although custom list views for custom objects are included.
- Only the following Administration settings in Experience Workspaces are included.
- Change password page
- Forgot password page
- Home page
- Login page
- Allow employees to log in directly to an Experience Cloud site option
- The following items aren’t included when you export an Experience Builder template. After
you import the template and use it to create an Experience Builder site in the destination org,
you must manually reconfigure these items.
- Most Administration settings (except for the settings already listed).
- Experience Builder settings, including head markup and the Google Tracking ID.
- Custom theme layout components that aren’t listed in Settings | Theme | Configure aren’t included. For theme layout components to be included, you don’t have to assign them to a page.
- Custom styles in the CSS editor.
- Localized content for multilingual sites.
- Non-default page variations; only default page variations are included. If a page doesn’t have a default variation, the page is excluded. For example, if a page has two variations that are both set to audience-based visibility, then the page is excluded entirely.
- If you upgrade a managed template package, existing sites that are based on the upgraded template aren’t updated.
- Some pages in a template are available only when a feature is enabled in your org—for example, the Article Detail page requires Salesforce Knowledge. An exported template includes just the pages that exist in your site at the time of export. Any site that’s built using the exported template includes only those same pages. For further assistance, contact Salesforce Customer Support.
Note Some components show errors when you deploy or export a site as a template and require you
to manually configure the component’s properties in Builder. For example, to set filters for the
Object Home and Record List components in your exported site, navigate to the component
properties. Then reconfigure the filter that you want to use from the dropdown menu.
Export and Package a Theme
- You can export a custom Experience Builder theme from Experience Builder but a standalone theme can’t be included in a Lightning Bolt Solution.
- An exported theme name must be unique.
- Custom theme layout components that aren’t listed in Settings | Theme | Configure aren’t included. For theme layout components to be included, you don’t have to assign them to a page.
- If you upgrade a managed theme package, existing sites that are based on the upgraded theme aren’t updated.
- When you export a theme from Experience Builder, the system removes non-alphanumeric characters from your theme name. For example, My Theme #2 becomes My_Theme_2.
Export and Package a Single Experience Builder Page
- The exported Experience Builder page name must be unique.
- When you export a page, the system generates a developer name (
devName) by prepending the site name and removing non-alphanumeric characters. For example, My #awesome page in the Acme site becomes Acme_My_awesome_page. Developer names longer than 80 characters are truncated. - When you export an Experience Builder page, its page variations aren’t included in the package. Export the page variations separately.
- Exported page variations use the naming convention
[Site Name]_[Page Name]_[Variation Name].Original Page Name Exported Page Name Exported Page Developer Name Coffee Fans Coffee Fans Acme_Coffee_Fans West Coast (page variation) Coffee Fans - West Coast Acme_Coffee_Fans_West_Coast East Coast (page variation) Coffee Fans - East Coast Acme_Coffee_Fans_East_Coast - For images in the Rich Content Editor, we export the version used in the editor, which isn’t necessarily the latest version of the asset file.
- Audience-based visibility criteria aren’t included in the export process. Manually reenter this information after importing the page to the site in the destination org.
- You can’t export individual login pages.
- Export assigns a developer name from the site, object, and page type (detail, list, or related list). You can’t rename object pages during export the way you can some standard pages, and trying to export the same object page again can fail if that exported page already exists.
- If a site already has object pages for an object, the New Page dialog doesn’t include that object to choose from again. This prevents an exported object sub-page from showing up as a separate selectable page. Standard pages can list multiple exported layouts in the wizard; object pages don’t behave the same way. If several exported object pages exist for one object in Setup, remove unneeded pages to avoid ambiguity.