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: LockerService and Stricter CSP
Analyze and Improve Community Performance (Developer Preview)
Community Migration, Packaging, and Distribution
Migrate Your Community with Change Sets
Considerations for Migrating Communities with Change Sets
Lightning Bolt Solutions: Build Once, Then Distribute and Reuse
PDF

Newer Version Available

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

Considerations for Migrating Communities with Change Sets

Keep the following considerations and limitations in mind when migrating your Lightning or Salesforce Tabs + Visualforce community with change sets.
Available in: Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions

  • For Communities, you can only make updates with change sets, which means that you can’t create a community directly from an inbound change set. Instead, in the target org, first create a community with the same name and template version, and then deploy the inbound change set.
  • When you deploy an inbound change set, it overwrites the community in the target org. So although you can’t use a change set to delete a component, such as a community, you can delete the pages within the community. For example, let’s say you delete pages from a community in sandbox and then create an updated outbound change set. When you redeploy the change set in a target org, such as production, the pages are also deleted there.
  • Navigation Menu items are supported. However, for 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.
  • If you update the community template in the source org to unify its branding properties, ensure that the template is also updated in the target org before deploying the change set.
  • Only the following Administration settings in Workspaces or Community Management are supported.
    • Change password page
    • Forgot password page
    • Home page
    • Login page
    • Allow internal users to log in directly to the community option

    For communities created in a sandbox org before the Summer ’17 release, you must resave these settings prior to migration to transfer them successfully. Similarly, reselect all images used in the Branding panel.

    Note

  • The following items work only with published pages, so until you publish your community in the target org:
    • Navigation Menu items that point to community pages appear to be broken
    • Settings for the change password, forgot password, home, and login pages appear to return to their default values
  • The following items aren’t supported. Manually reconfigure them after you deploy the inbound change set.
    • Most Administration settings in Workspaces or Community Management (except for the settings already listed)
    • Page variations and audience targeting
    • Navigational and featured topics
    • Languages
    • Advanced settings in Community Builder, such as in Google Analytics