Experience Cloud Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Get Up to Speed with Experience Builder Sites
Develop Experience Builder Sites: The Basics
Brand Your Aura Site
Develop Secure Sites: Authenticated and Guest Users
Develop Secure Sites: CSP, LWS, and Lightning Locker
Analyze and Improve Experience Builder Site Performance
Add Pardot Tracking to Your Experience Builder Site
Use a CMS with Your Experience Builder Site
Report on Deflections: The Deflection Signals Framework
Deploy an Experience Cloud Site from Sandbox to Production
Deploy Your Experience Cloud Site with Change Sets
Deploy A Full Experience Cloud Site with Change Sets
Deploy Partial Experience Cloud Site Content with Change Sets
Considerations for Deploying Experience Cloud Sites with Change Sets
Deploy Your Experience Cloud Site with the Metadata API
ExperienceBundle for Experience Builder Sites
Avoid Deployment Issues When Moving to Enhanced LWR Sites
Considerations for Deploying Authenticated LWR Sites
PDF

Deploy Partial Experience Cloud Site Content with Change Sets

Use change sets to move individual Experience Cloud components and content between related orgs that have a deployment connection, such as your sandbox and production orgs. Create and test changes in your test environment, and then migrate only those changes to production when they’re ready.
Available in: Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Enterprise, Performance, and Unlimited Editions

User Permissions Needed
To customize or publish an Experience Cloud site: Create and Set Up Experiences
To edit deployment connections and use inbound change sets: Deploy Change Sets AND Modify All Data

If a user requires access only to metadata for deployments, you can enable the Modify Metadata Through Metadata API Functions permission. This permission gives such users the access they need for deployments without providing access to org data. For details, see “Modify Metadata Through Metadata API Functions Permission” in Salesforce Help.
To use outbound change sets: Create and Upload Change Sets, Create AppExchange Packages, AND Upload AppExchange Packages

Partial deployment with change sets is available for enhanced LWR sites created in Winter ’23 and later.

You can use change sets to move partial content for Experience Builder sites using the Digital Experiences component type.

  1. Create and test your site in your preferred test org, such as a sandbox.
  2. From Setup in your test org, in the Quick Find box, enter Outbound Change Sets, and then select Outbound Change Sets.
  3. Create a change set, and click Add in the Change Set Components section.
  4. Select the Digital Experience component type.
  5. Select the content that you want to deploy from the list of components, and then click Add To Change Set.
    • To identify which enhanced LWR site each listed component belongs to, use the Type column. The Type column uses the naming convention site/MySiteName.
    • To identify what content each listed component represents, use the Name column. The Name column uses the naming convention sfdc_cms__<contentType>/<contentName>. For example, the name sfdc_cms__brandingSet/Build_Your_Own_LWR represents a branding set named Build Your Own LWR.

    Tip

  6. 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.
  7. From Setup, select Inbound Change Sets, and find the change set that you uploaded from your source org.
  8. Validate and deploy the change set to make it available in the target org.

    When you deploy an inbound change set, it overrides the corresponding site content in the target org.

    Warning

  9. Manually reconfigure any unsupported items in the target org site.
  10. To make sure that everything works as expected, test your site. Then publish your changes to go live.