NavigationMenus on experience cloud sites with spaces in the name throw deployment error after Spring '22 Upgrade
Last updated Today ·Reference W-10933976 ·Reported By 40 users
Summary
When deploying NavigationMenus in sites with spaces in the site name, the error "Name: The Navigation Link Set API Name can only contain underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores." is thrown when the default file names are used.
For example, NavigationMenus for an experience cloud site with the name "Site Name with Spaces" receives the file "SFDC_Default_Navigation_Site Name with Spaces.navigationMenu".
When any changes are made to this file (changing label names, etc.) and the changes are deployed, the error is thrown because the name contains spaces.
Repro
Note: these reproduction steps are for deployments using Workbench, but the error has been observed when the file name contains spaces regardless of deployment method.
1. Retrieve NavigationMenus:
a) Log in to workbench
b) Go to migration tab > retrieve
c) Upload a "package.xml" to retrieve all NavigationMenus. The retrieved zip will have a file in the navigationMenus folder called "SFDC_Default_Navigation_Site Name With Spaces.navigationMenu" where "Site Name With Spaces" is the site name
2. Make any changes to that file, and remove all other files in the navigationMenus folder
3. Zip up the parent folder and deploy using workbench (migration tab > deploy)
a) Upload the zip file, and check "Single Package"
b) Hit Continue, then Deploy
3. Receive the error: "Name: The Navigation Link Set API Name can only contain underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores."
Workaround
There is no workaround available at this time.
Reported By (40)

















Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.