Validation Error 1:
"<xxx> wasn’t deployed because ExperienceBundle isn’t enabled for Aura sites. To enable ExperienceBundle, in Setup, select Enable ExperienceBundle Metadata API in Digital Experiences | Settings."
In this example <xxx> is a reference to a specific metadata component, e.g. a site (on below example it is JacobSite1).
Resolution
Navigate to both source and target orgs and check the Enable ExperienceBundle Metadata API checkbox.
Validation Error 2:
"The value for urlPathPrefix in ExperienceBundle isn't valid. Check the value and try again."
Resolution
Remove any Site.com metadata from the deployment package.
Validation Error 3:
"The reportId property of component <xxx> references an object with the ID value <yyy>. Occasionally, when deployed to a destination org, ID values can become invalid—for example, if the referenced ID doesn’t exist in the destination org. If you encounter component issues in your destination org, verify that the ID values are correct."
Resolution
Hopefully, this is a quick fix where you need to disable Treat warnings as errors checkbox on the Deployment settings page in Gearset.
And then once done, re-validate the deployment package in our app.
Validation error 4:
"The currentThemeId property in <xxx>.json is null or points to a non-theme component. Update currentThemeId to point to the site's theme and try again.
An example of the error message in our app would look as below:
The currentThemeId property in <xxx>.json is null or points to a non-theme component. Update currentThemeId to point to the site's theme and try again
We found that the currentThemeId could be different from org to org and the mismatch could result in this error.
You can try to edit that value in your deployment package to match the target org to see if it works. Or temporarily use Environment variable functionality to match the source value's ID.
Validation error 5:
"The navigation menu Default_Navigation doesn’t exist.. Check your file and try again."
For this error, one of the customers contacted Salesforce and provided the below steps to resolve this issue.
"Looks like those errors are specific to the sandbox data you are deploying to. The number of Experience Sites you have will determine the Developer names of standard Navigation Menus."
User explained the workaround they applied was:
"I needed to update the Developer Names from this query in the Developer Console: SELECT Id, DeveloperName, MasterLabel, Network.Name FROM NavigationLinkSet.
Then the deployment went fine."
Validation error 6:
"We couldn't validate componentAttributes in <xxx> for component <yyy>. Error: attribute [quickActionName]: Attribute is required and missing a value. Check your file and try again."
For this error, we found that in the XML file, the QuickActionName can be empty as below. Causing Salesforce to say that it's missing a value.
One of the customers found these steps to resolve this issue:
To resolve the missing Global Action issue in Experience Builder, check if the Global Action field is set. If not, ensure the "Case" Quick Action has a Record Type assigned in Case Object Manager.
Then, verify that the Partner Community User Profile has the correct Case Record Type and Create, Read, and Edit permissions.
Add the Quick Action to the Global Publisher Layout in Setup → Global Actions → Publisher Layouts.
Finally, update the selection in Experience Builder, save, and publish the site.
Other errors we have seen during deployments
Note: These errors were only seen when attempting to deploy components of which the XML had been modified directly before deployment.
Error messages:
In field: Site - no CustomSite named <xxx> foundIn field: Network - no Network named <xxx> foundThe Default Web Address must be alphanumeric.
These errors occurred when an edit was made directly to the XML of the Custom site and Network metadata, specifically a /s was added in onto the urlPathPrefix.
To resolve these errors remove /s (or any such extras) from the field urlPathPrefix in CustomSite and Network.
To see how to edit the deployment package see this article.
Disclaimer: All the above errors are returned by Salesforce directly, rather than Gearset. Even so, we offer guidance based on our combined experience with the Metadata API. Where possible, we try to help guide you to fix or avoid this error. In the case that this isn't possible, we may need to direct you to Salesforce support for further clarification.