Lightning Communities Developer Guide
jNewer Version Available
Export and Packaging Considerations for Lightning Bolt Solutions
Before you export a customized template or page as a Lightning Bolt solution, keep the following
considerations and limitations in mind.
| Available in: Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
Single Page Export and Packaging
- The exported page name must be unique.
- When you export a page, the system automatically generates a developer name (devName) for it by prepending the community name and removing any non-alphanumeric characters. For example, My #awesome page in the Acme community becomes Acme_My_awesome_page. Developer names longer than 80 characters are truncated.
- Exported page variations use the naming convention [Community
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 is not necessary 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 community in the destination org.
- When you export a page, its page variations aren’t included in the package; you must export them separately.
- You can’t export individual login pages.
Template Export and Packaging
- The exported template name must be unique.
- When you export a template, the system removes any non-alphanumeric characters from the template and page names. For example, My Template #2 becomes My_Template_2.
- In the Community Creation wizard, the template author (for example, by Salesforce) for exported and imported templates differs. When you export a template, your org name is shown within your own org. When you import a template, the publisher name of the package is shown.
- 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.
- Only the following Administration settings (in Workspaces or Community Management) are included.
- Change password page
- Forgot password page
- Home page
- Login page
- Allow internal users to log in directly to the community option
- The following items are not included when you export a template. After you import the
template and use it create a community in the destination org, you must manually reconfigure
these items.
- Most Administration settings (except for the settings already listed).
- Community Builder settings, including head markup and the Google Tracking ID.
- Custom theme layouts that aren’t in use. Only theme layouts that are selected in are included.
- Custom styles in the CSS editor.
- Localized content for multilingual communities.
- Non-default page variations; only default page variations are included. If a page doesn’t have a default variation—for example, a page with two variations that are both set to audience-based visibility—the page is excluded entirely.
- If you upgrade a managed template package, existing communities that are based on the upgraded template aren’t updated.