Skip to main content
12 votes
Accepted

How do I package an upgradable Experience Builder Site?

This seems so simple on the face of it, but ends up quite difficult to achieve. I did manage, and on the way learned quite a bit. The main learning points: You have to have just the right metadata ...
Phil W's user avatar
  • 38.2k
9 votes
Accepted

Salesforce Error Publishing Community 1715759908

Salesforce Support got back to me and they said that this was most likely caused because during the deployment, Navigation Menu Item records were created without having a DraftRowId set. As a solution:...
Z33dawg's user avatar
  • 1,441
6 votes
Accepted

Error creating scratch orgs with "Communities" enabled

The issue you are facing is related to ongoing Known issue. Our Salesforce Team is working to fix it. The workaround would be to switch to previous release by using "release": "Previous&...
Swetha Maddali's user avatar
5 votes
Accepted

Platform error when deploying Experience Bundle (sites.data.store.ConcurrentEditDetectedException ORA-20612)

We found that, when we entered the site in the target org, this popup appeared After clicking reload and publishing the site, we were able to deploy the site Hope it helps anyone in the same ...
mnunezdm's user avatar
  • 919
4 votes
Accepted

Error when deploy experience bundle community using Ant migration tool

This happens if you have a custom aura/LWC theme component but it wasn't part of the package or not already deployed in the org or doesnt implement forceCommunityThemelayout. Search the buildYourOwn....
Shibi Chakkaravarthy's user avatar
4 votes

Deployment Problems Experience (Network - no Network named "...." found)

The issue is because you have not added Network metadata to the build. Make sure to add Network metadata along with CustomSite and the ExperienceBundle. Check the docs here.
Mohith Shrivastava's user avatar
3 votes

Unable to retrieve ExperienceBundle from developer edition org

I suggest you check if the metadata you want is the DigitalExperienceBundle (documentation) because it might be the Enhanced LWR site you have created. I also suggest you review this documentation ...
Jeferson Chaves's user avatar
3 votes
Accepted

Invalid IOS url - Experience Bundle Site.com Deployment Error

It is a recent issue Salesforce is having due to their recent updates. Quoted from Salesforce: "It is coming to our attention since after some new updates and patches. It is causing this problem. ...
Vin Tang's user avatar
2 votes
Accepted

Error on Experience Cloud filter during deploy (Account.Id on standard Chart component)

ReportIds attribute varies between the environments. Hence the only way to deploy this is by adding the relevant report to the environment first and then noting its ID and then in the views/home.json ...
Mohith Shrivastava's user avatar
2 votes
Accepted

Communities error when building new package version for code coverage

As of now(v50.0), communities are not supported with the Unlocked Packages. You can check the coverage for metadata elements here - Metadata Coverage However, you can deploy(and publish) the ...
Ysr Shk's user avatar
  • 3,175
2 votes
Accepted

Experience Bundle deploy- The activeViewId for the XXX route in .../routes/reportBuilder.json doesn’t point to a valid view. Update activeViewId

OK, this was user error My deployment tool in this use case was Gearset that displays for selection each Experience Bundle folder/file as a separate row in their Difference Viewer While I had included ...
cropredy's user avatar
  • 73.3k
1 vote
Accepted

What to use for an LWR DigitalExperience - ExperienceBundle or DigitalExperienceBundle?

You shouldn't let the word "beta" scare you off. Anything that's gotten as far as beta means "it mostly works but might have some weird quirks or limitations." The main reason for ...
sfdcfox's user avatar
  • 502k
1 vote
Accepted

Deploying Experience Bundles fails with: "The topicId property of component xxxx references an object with the ID value 0TOxxxxx

This was not obvious at first. Steps to Solution Hopefully, your metadata for your Experience Site is in your VCS and is up-to-date. If not, create a project (or use Workbench) and download the ...
cropredy's user avatar
  • 73.3k
1 vote

How to uninstall Unlocked Package that contains Experience Bundle

Remove manually reference from Unlocked package to the Digital Experience site. Also it is a good idea to archive the Digital Experience Site since you can't actually remove it. After references from ...
Patlatus's user avatar
  • 17.8k
1 vote
Accepted

isLockerServiceEnabled cannot be changed to false until isRelaxedCSPLevel is set to true

As communicated on the support case, the issue you are facing has been identified as a bug by the salesforce product team. While there is no workaround at the moment, the ETA for the fix is Spring'23(...
Swetha Maddali's user avatar
1 vote
Accepted

Strange error when I want to deploy community to scratch org. Is it sfdx bug or I missing something?

As per the documentation use the below If you’re using the Service Not Available page in a scratch org, add PublishExpBuilderBasedSna and PublishAuraExpBuilderBasedSna features to your scratch org ...
Mohith Shrivastava's user avatar
1 vote
Accepted

Service Not Available Page in Experience Bundle deployment issues

To provide just this aspect for future searchers, here's my experience with this issue when I got it with my packaged experience builder site: I kept my sfdx-project.json's sourceApiVersion as 51.0. ...
Phil W's user avatar
  • 38.2k
1 vote

How do we deploy an Experience Bundle to a scratch org properly?

I’m late to the party but I want to share that this problem can indeed be solved in an automated fashion using CumulusCI. For anyone who’s interested, you’ll need to configure your cumulusci.yml to: ...
David Bingham's user avatar
1 vote
Accepted

Community deplyment issues related to componentName

I found the problem, whenever you face this kind of insignificant error try to re-check your change set to see if you are missing a dependency and clone your change set and add those dependencies to ...
Mohamed elqandili's user avatar
1 vote

Error when deploy experience bundle community using Ant migration tool

In case of deploying to a scratch org when facing the same error message, it helped to use the -f switch of the force:source:push command: $ sfdx force:source:push -fg
Johannes Heinen's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible