... a contemporary perspective on how to integrate B2C Commerce and the Salesforce Customer 360 Platform to power frictionless customer experiences in the B2C domain.
Describe the bug
The validator says that B2C_INSTANCENAME "must start with a letter -- and only contain letters and numbers"
In a world of On Demand Sandboxes this is not true.
All of my sandbox names of of the format [4 letter REALM_ID]-[3 digit number].dx.commercecloud.salesforce.com.
These names are automatically assigned.
To Reproduce
Steps to reproduce the behavior:
Create a SFCC ODS
follow the steps to set up the B2C Commerce Configuration Properties
Run the validations. Especially 'npm run crm-sync:b2c:verify'
notice the validation error that is wrong.
Expected behavior
Not to have a validation error on a system generated name.
Screenshots
Your local environment details:
Node version (node -v): v12.21.0
NPM version (npm -v): 6.14.11
SFDX version (sfdx -v) sfdx-cli/7.194.1 win32-x64 node-v18.15.0
Your remote environment details:
Salesforce B2C Commerce version: Version: 23.10 Last Updated: Oct 9, 2023 (Compatibility Mode: 22.7)
Salesforce Core version: [e.g. 52]
Additional context
Add any other context about the problem here.
Describe the bug The validator says that B2C_INSTANCENAME "must start with a letter -- and only contain letters and numbers" In a world of On Demand Sandboxes this is not true. All of my sandbox names of of the format [4 letter REALM_ID]-[3 digit number].dx.commercecloud.salesforce.com. These names are automatically assigned.
To Reproduce Steps to reproduce the behavior:
Expected behavior Not to have a validation error on a system generated name.
Screenshots
Your local environment details:
node -v
): v12.21.0npm -v
): 6.14.11sfdx -v
) sfdx-cli/7.194.1 win32-x64 node-v18.15.0Your remote environment details:
Additional context Add any other context about the problem here.