I have enabled the ExperienceBundle metadata type and am using SFDX-git-delta to generate package.xml files. SFDX-git-delta will generate a package.xml file like the following when one of the files in the experiences directory changes:
<?xml version="1.0" encoding="UTF-8"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"> <types> <members>CommunityMdName</members> <name>ExperienceBundle</name> </types> <version>51.0</version> </Package>
When I run
sfdx force:source:deploy -x myPackage.xml -u firstname.lastname@example.org nothing is deployed.
- How can I get a package.xml based deployment to deploy the ExperienceBundle?
- Is it possible to only deploy the changes in the ExeperienceBundle while using the package.xml / -x (e.g., 3 view json files were changed, so only deploy those?)
I debugged with
export SFDX_MDAPI_TEMP_DIR=metadata and see that the package.xml file that sfdx generates (note this is not the one sfdx-git-delta creates) doesn't include the ExperienceBundle type, despite it being in the source package.xml (the one sfdx-git-delta creates) and the source folder (main/default/experiences/CommunityMdName/..). SFDX also doesn't copy over the experiences directory.
I would really like to be able to use SFDX-git-delta + ExperienceBundle metadata.
Sidenote: It deploys fine when doing from the source directly with no package.xml, i.e., when using the -p option