You are here:
Troubleshoot Metadata Deployment Errors in Experience Cloud Sites
Solve issues that can arise when deploying LWR and Aura sites with ExperienceBundle or enhanced LWR sites with DigitalExperienceBundle.
Required Editions
| Available in: Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
| Applies to: LWR and Aura sites |
| Error Message | Cause | Solution |
|---|---|---|
| Specify a unique ID for each component in this view. | In DigitalExperienceBundle, each component in a view must have a unique ID. In this case, two or more components have the same ID. | Retrieve the metadata from both the source and target orgs using DigitalExperienceBundle. In the view that caused the error, in both the source and the target org, search for components with matching IDs. When you find a matching ID, manually update it by altering a couple of characters to ensure that each component has a unique identifier. |
| The devName of an existing route can’t be changed. Revert the devName of the generated_route_id route back to its original value and try again. | In ExperienceBundle, devName represents a unique API name that’s automatically generated for a route when you create it. devName is a required value that must not be changed. This error occurs if the value was altered in some way. | Review any recent modifications or customizations related to standard component functionality. Determine how and why the name was altered, and revert the name to its original value. Alternatively, consider using SiteDotCom for your deployment instead of ExperienceBundle. |
| We couldn't validate property_name in file_path.json for component component_id. Error: specific_error_information | In ExperienceBundle, this error occurs when the site configuration in the source org doesn't match the target org. For example, let's say the theme in the source org is using Default_User_Profile_Menu, but the theme in the target org is using Default_User_Profile_Menu1. | Ensure that the sites in the source and target orgs use the same configuration. For example, if the specific error information mentions that a component is missing, ensure that the component names match in both orgs. |
| You seem to be missing the property isLockerServiceEnabled in site_name/config/mainAppPage.json with component ID component_id. | In ExperienceBundle, this error occurs when the isLockerServiceEnabled property in the site's config/mainAppPage.json file is missing. | Add "isRelaxedCSPLevel" : false to the
config/mainAppPage.json file. |
| Your site needs a route with route type route_type. | This issue can occur due for various reasons. Reason 1: There's a discrepancy between the site features or custom objects that are enabled in the source org and the target org. Because of this difference, the ExperienceBundle retrieval process can't include the necessary object- or feature-related files from the source org. However, the target org requires these files. |
Enable the relevant permission in the source org. Then retrieve ExperienceBundle again and deploy the updated bundle to the target org. If it isn't possible to enable the permission in the source org, you can disable the permission on the target org instead. Keep in mind that, as a result, permission-related features can be missing in the deployed site. |
| Reason 2: Each site template includes default routes types that are required. This issue can occur if the route type was somehow deleted or renamed. | Update the site_name.site-meta.xml file to include a route with the correct route type. Ensure that the route configuration aligns with the intended functionality of the site. |
