[BUG] ... Sandbox ( Not-Scratch Org ) deployment error

[amitastreait]

Describe the bug I am trying to implement Order of Customer Behalf for my Commerce Cloud Project. I have followed all the steps and got the error while deploying the codebase to Sandbox Org.

DEPLOY PROGRESS | ████████████████████████████████████████ | 573/573 Components *** Deploying v52.0 metadata with SOAP API v53.0 connection *** === Component Failures [3]SAI Type Name Problem ───── ────────────────────────────────────────── ─────────────────────────────────────────────────────────────────────────────────────────────────────────────── Error Contact lookupPhoneDialogsAdditionalFields ACCOUNT.PHONE1 not found Error Contact.Non_B2C_Commerce_Customer_Profiles Could not resolve list view column: ACCOUNT.RECORDTYPE (770:16) Error bfvg_B2C_OOBO Error parsing file: A decimal representation must immediately follow the "&#" in a character reference. (11:62)

ERROR running force:source:deploy: Deploy failed.

To Reproduce Steps to reproduce the behavior: run sfdx force:source:deploy -p src/sfdc/base command and see the error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots

Your local environment details:

• Node version (node -v): v16.13.2
• NPM version (npm -v) : 8.1.2
• SFDX version (sfdx -v) : sfdx-cli/7.134.0 win32-x64 node-v16.13.2

Your remote environment details:

• Salesforce B2C Commerce version: 21.7
• Salesforce Core version: 54

Additional context NA

Please help me with this as I have a Go-Live date this weekend and this is must to have functionality!

[amitastreait]

Update 1

The named credentials error is gone as it was due to an invalid password. But there are still these remaining error

We have person account enabled for our Salesforce Org so We have Record Type Enabled

[amitastreait]

Update 2

I have also found that in the Contact Object file there are additional phone fields that I am not able to find in the contact object or account object.

In this something which is missing from your side. Please suggest.

[ericszulc]

Hi @amitastreait , if those fields are not available in your org, I would simply remove them from list view and search layouts.