Lightning Communities Developer Guide

Get Up to Speed with Lightning Communities
Develop Lightning Communities: The Basics
Customize the Look and Feel of a Lightning Template
Example: Build a Condensed Theme Layout Component
Develop Secure Code: Locker Service and Stricter CSP
Analyze and Improve Community Performance
Connect Your Community to Your Content Management System
Deploy a Community from Sandbox to Production
PDF

Newer Version Available

This content describes an older version of this product. View Latest

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.
Available in: Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions

We recommend using managed packages to avoid naming conflicts with other packages in your customer’s org or your own.

Tip

Add Custom Apps

  • When you include apps in a Lightning Bolt Solution, follow general guidelines in the ISVforce Guide 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 a Lightning Community Template

  • You can export a custom Lightning Community template in a Lightning Bolt Solution, but including a template is not required.
  • An exported template name must be unique.
  • When you export a template, the system removes non-alphanumeric characters from 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) differs for an exported and imported template. 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 included.
  • 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 Lightning Community template. After you import the template and use it to 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 Settings | Theme 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, 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 communities that are based on the upgraded template aren’t updated.

Export and Package a Single Community Page

  • The exported Community page name must be unique.
  • When you export a page, the system generates a developer name (devName) by prepending the community name and removing 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].

    When you export a Lightning Community page, its page variations aren’t included in the package. Export the page variations separately.

    Note

    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 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 community in the destination org.
  • You can’t export individual login pages.