Toggle Side Panel
Close search

Activity › Forums › Salesforce® Discussions › How to deploy the Lightning components and Lightning Pages (Inside Community Builder) from Sandbox to Prod?

Tagged: , , , , , ,

  • Piyush

    Member
    April 25, 2016 at 10:42 AM

    Hello Hazel ,

    Follow this link for deploying lightning Component and pages from Sandbox to Prod.

    https://blogs.perficient.com/salesforce/2015/12/22/deploy-community-builder-templates-in-3-simple-steps/

     

  • [adinserter block='9']

  • Parul

    Member
    September 20, 2018 at 1:00 AM

    Hi,

    Step 1:

    Use change sets to move all custom lightning components you are referencing in the community from the sandbox to production, as well as any metadata that you setup outside of the Community Builder (welcome email templates, workflow rules, profiles, permission sets, etc). If you skip this step, it will still allow you to deploy the community and will appear to be successful, but you will see an internal server error in the Community Builder and will not be able to make any updates until you have moved the missing components into production. I highly recommend creating a deployment template and filling it in as you build your community to ensure nothing is forgotten at the time of deployment; it is an important part of our methodology at Perficient and ensures smooth deployments.
    Step 2:

    From your sandbox, navigate to the Site.com Studio and locate the toolbar. Click the arrow next to the widget icon and select to ‘Export This Site’ from the sandbox. Then go into production and create a new community, selecting the same version of the template; going from a Spring ’16 Napili template in sandbox and moving Winter ’16 production environment will not work. You need to go from Winter’ 16 in sandbox to Winter ’16 in production. All customization performed inside the Community Builder will move over.
    Step 3:

    Go to the Community Management console and update your administrative settings, topics, moderation criteria, etc. as these do not carry over automatically.

  • shariq

    Member
    September 20, 2018 at 7:32 PM

    Hi,

    Found this online -

    Use change sets to move your community between related orgs that have a deployment connection, such as your sandbox and production orgs. Create, customize, and test your community in your test environment and then migrate the community to production when testing is complete.

    You can use change sets to move Lightning communities and Salesforce Tabs + Visualforce communities.
    Create and test your community in your preferred test org, such as sandbox.
    From Setup in your test org, enter Outbound Change Sets in the Quick Find box, and then select Outbound Change Sets.
    Create a change set, and click Add in the Change Set Components section.
    Select the Network component type, choose your community, and then click Add to Change Set.
    To add dependent items, click View/Add Dependencies. We recommend selecting all the dependencies listed.

    For navigation menus that link to standard objects, custom list views aren’t included as dependencies. Manually add the custom list view to your change list.
    Manually add new or modified profiles or permission sets referenced in Administration | Members.
    The list of dependencies has two Site.com items—MyCommunityName and MyCommunityName1. MyCommunityName holds the various Visualforce pages that you can set in Administration (in Community Workspaces or Community Management). MyCommunityName1 includes the pages from Community Builder.

    Click Upload and select your target org, such as production.Make sure that the target org allows inbound connections. The inbound and outbound orgs must have a deployment connection.
    From Setup, select Inbound Change Sets and find the change set that you uploaded from your source org.
    Validate and deploy the change set to make it available in the target org.

    When you deploy an inbound change set, it overwrites the community in the target org.
    Manually reconfigure any unsupported items in the target org community.
    Add data for your community, and test it to make sure that everything works as expected. Then publish your changes to go live.

    Hope this helps.

Log In to reply.

Popular Salesforce Blogs

Popular Salesforce Videos