I'm using the Metadata API with a Salesforce-focused DevOps tool to deploy new and updated pages on an #LWR (Build Your Own) site (with #Experiencebundle) from a sandbox to another sandbox. I've got a set of changes that includes both routes AND views, but upon validating the deployment I'm getting errors on many of the pages generated by the LWR site in the sandbox. Here are a few examples:
File name: digitalExperiences/site/Conference1.digitalExperience, Component name: site/Conference1.sfdc_cms__route/Session_Related_List__c (Line: null: Column:null) :
Message: The value of the $.routeType property is invalid.
File name: digitalExperiences/site/Conference1.digitalExperience, Component name: site/Conference1.sfdc_cms__route/Session_List__c (Line: null: Column:null) :
Message: The value of the $.routeType property is invalid.
File name: digitalExperiences/site/Conference1.digitalExperience, Component name: site/Conference1.sfdc_cms__route/Session_Detail__c (Line: null: Column:null) :
Message: The value of the $.routeType property is invalid.
Looking into the relevant metadata files, all three route content.json files have the same routeType:
"routeType" : "relatedlist-a2Q",
There certainly are corresponding views for each route on the deployment. This strikes me as a bit odd, since the route type should work, and the custom object is both in the branch and is already in the target sandbox.
I'm curious what the #Metadata API is doing to validate here, since I can't figure out how it's validating that and I can find little documentation on that specific error.
@George Abboud - Not sure if you've run into this deploying LWR sites before?
@Joe Morse FYI, I already created an Idea for this already as we also struggle with this:
https://ideas.salesforce.com/s/idea/a0B8W00000PtxZKUAZ/enhanced-lwr-sites-object-pages-should-use-object-api-name-and-not-object-prefix so we don't create duplicate
I suggest reintroducing the objectApiName attribute like the "old" LWR metadata has. This is a very needed change in the metadata structure for us as well, as we currently need to script our way out of deployment errors by first querying the objectAPIPrefix in the Target and then replacing the routes before deployment :/
So please give it an upvote and tell your team the same! :)
Keep us updated with the progress in the email thread!
