I'm trying to create an object page for a custom object in an enhanced LWR Site. In the "old" LWR metadata structure (route), this is specified both by the routeType and the objectApiName attributes:
However, in the enhanced LWR metadata structure (route), I can only use the routeType attribute. objectApiName is not defined in the schema:
The problem is that the object prefix (detail-a1o) of our custom object is different in our scratch orgs and our sandboxes. This means that the object subpages are listed under the wrong object as shown below!
Scratch orgs:
Sandboxes:
Is there another way of setting the correct object reference in Enhanced LWR routes or is this a bug?
For enhanced LWR sites, instead of having a separate objectApiName, we embed this information in routeType itself.
The following format change has been made last year and should hopefully address the challenge described above.
Example: For a custom object with objectApiName: helperEntity, the routeType of the detail would be detail-helperEntity__c.
Please note a fresh retrieve is required to retrieve the new format.
Please let us know if you are still running into a problem
@Kai Amundsen. cc @George Abboud @David Green @Geno Mathew
