#Digital Experience10 discussing

@Rahul Kumar

try checking these threads -  

Hi @Shanika Nishani

Why this happens 

The routes.json dynamic-route syntax you may have seen in Salesforce docs applies to pro-code LWR apps built with the standalone LWR framework/CLI (outside Experience Cloud entirely) not to LWR sites built in Experience Builder. In Experience Builder, you don't get direct access to routes.json; the platform generates routing config from what you set in the Pages panel, and that UI only accepts static, hyphenated paths. 

The one built-in exception 

Object/Record Detail pages do support a dynamic segment automatically e.g. /s/product/{recordId} or /s/product/{urlName} but only because that's a special out-of-the-box "Object Page" type tied to a Supported Object via the UI API. You don't configure that path pattern yourself; it comes for free with that page type. It won't generalize to an arbitrary custom page. 

Practical workarounds 

1. Query parameters (supported, no workaround needed) /test?QP=testRecord, read via CurrentPageReference in your LWC. This is the intended mechanism for passing dynamic values to a custom LWR page.
2. Edge/CDN URL rewrite if your custom domain sits behind a CDN or reverse proxy you control (Cloudflare, Akamai, CloudFront, etc.), add a rewrite rule that maps /test/testRecord → /test?QP=testRecord before the request hits Salesforce. The browser URL stays pretty; Salesforce still only ever sees the query-param version. This is the most common way teams get "clean URLs" on Experience Cloud today.
3. Object Page pattern, generalized if what you actually want is "detail page keyed by a record's URL-friendly name," consider modeling it as a real Object Page against a Supported Object rather than a generic custom page then you inherit the dynamic-path behavior natively instead of fighting the custom-page path field.
4. True pro-code LWR if dynamic path routing is a hard requirement, that's a signal this isn't a fit for an Experience Builder-managed site at all; a decoupled/headless approach (LWR OSS app, or a separate front-end calling Salesforce APIs) gives you full routes.json control, at the cost of losing Experience Builder's drag-and-drop admin experience.

Given the trade-offs, most teams end up on option 2 (CDN rewrite) since it needs zero Salesforce-side changes and keeps admins working in Experience Builder normally. If you want to go that route, worth confirming first whether you're using Salesforce's own domain/CDN or a custom DNS setup in front of it that determines whether you even have a layer available to add the rewrite rule. 

I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

Hey Vishal, 

This matches a documented Salesforce Known Issue: Internal Server Error in Experience Builder when creating/accessing page variations. It's a recognized platform bug tied to how the builder handles new page creation for certain page types, not something wrong with your API name or setup. 

Workaround from Salesforce's own known issue documentation: 

1. Open Experience Builder, open the Pages menu 

2. Locate the affected page, click the three dots next to it, go to Page Properties 

3. From there, try creating the page fresh as a page variation with a basic/blank layout rather than through the standard "New Page" flow 

If this workaround doesn't resolve it for you, per the same known issue, the recommended next step is opening a case with Salesforce Support directly, referencing this as matching the known "Internal Server Error in Experience Builder when accessing page variations" issue and providing your specific Error ID (628191604-286554) so they can trace it against the root cause already on file. 

Reference:

I have found the issue. 

For whatever reason following the "Create a Queue" step didn't produced a queue, which then made selecting "Category 1 Biking Queue" in the "Omni-Channel Routing type" in the "Create a Channel" step impossible. 

Trying to create a new queue resulted in an error when trying to enter the Routing Configuration for "Category 1 Biking" ("

No matches found."). So I had to click the search icon next to the input, then "Clear Search Results" to see a list of possible Routings in the Search Results (and click the Category 1 Biking). 

After that I saw the new created queue, and the rest of the process could be completed.

Hi all! I've got a followup article that was recently published on Salesforce Ben which covers some of the neat things you can do with the Columns component. The article uses the same demo website shown in the Show Me How episode, and it goes into more detail about how to achieve the layouts you see in the website. 

https://www.salesforceben.com/how-to-use-salesforce-experience-builders-columns-component-like-a-pro/

If anyone has any questions about how to get similar layouts for your website, don't hesitate to reach out! I'm happy to help.