3

We've activated ExperienceBundle metadata for communities. However, there's a known issue with it that is preventing us from actually being able to deploy using that metadata. In order to avoid having to make manual changes until they fix it, can I revert back to just using SiteDotCom in my deployments?

The documentation doesn't seem to be very clear on this

After you enable ExperienceBundle, Metadata API calls (retrieve and deploy) and Salesforce DX operations (pull, push, and status) use the ExperienceBundle type instead of SiteDotCom.

However, it doesn't seem to imply there's anything stopping us from specifying SiteDotCom to pull and deploy from the API. Only thing is, I won't really be able to tell if it's actually kept up-to-date with community changes since activating the new metadata type.

I pulled the SiteDotCom metadata and the lastModifiedDate on the Community I'm looking at seems to imply it hasn't changed with our recent changes which makes me think it's no longer an accurate representation.

Improve this question

2 Answers 2

Reset to default
1

Talking to the Product Team, Here is what is recommend.

  • Disable experience bundle in settings
  • Retrieve the sitedotcom metadata type
  • Deploy the sitedotcom and other dependencies.
Improve this answer
2
  • Awesome, thanks. I can't believe I didn't think about disabling it again - I just assumed it was one of those all or none settings! Is there any info on what enable/disable actually does (might be another question!)
    – Kris Goncalves
    Commented May 15, 2020 at 15:20
  • Not sure but will check internally! Reach out to me for any feedback. Email shared!!
    – Mohith Shrivastava
    Commented May 15, 2020 at 15:22
2

The answer is yes.

I did get word from my support case where Tier 3 said SiteDotCom is still up-to-date even with ExperienceBundle enabled and I asked that they include that as a workaround for the known issue in the question as a way to get this documented (not sure if they will actually add this).

Regardless, the above prompted me to feel it was worth doing some test runs. I was still concerned by the lastModifiedDate, but I also found this idea which seems to confirm that manually published changes (which is what we did) don't accurately get reflected in the metadata types related to Community.

I deployed the SiteDotCom metadata to a sandbox and it appears it contained changes that happened after the lastModifiedDate so that confirms the metadata type is still an accurate representation of your community even after you've enabled ExperienceBundle regardless of what the timestamp says.

Also to note, the lastModifiedDate changes once you do deploy SiteDotCom in your target environment.

Improve this answer
1
  • Please reach out to me at [email protected] for any feedback on communities metadata. We are looking to improve the experience.
    – Mohith Shrivastava
    Commented May 15, 2020 at 14:53

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .