0

Getting an error: "Account.SalesforceCustomer Custom Field -Could not resolve standard field's name." when deploying to scratch org What feature should be enabled for this field to appear on Account object? Found one similar topic Account.SalesforceCustomer Could not resolve standard field's name. -Error but no answers

Scratch configuration:

"features": [
    "LiveAgent",
    "PersonAccounts",
    "Knowledge",
    "SurveyAdvancedFeatures",
    "MultiCurrency",
    "EntityTranslation"
  ],
  "settings": {
    "sharingSettings": {
      "enableAssetSharing": true
    },
    "territory2Settings": {
      "enableTerritoryManagement2": true
    },
    "surveySettings": {
      "enableSurvey": true
    },
    "knowledgeSettings": {
      "enableKnowledge": true,
      "defaultLanguage": "en_US",
      "enableLightningKnowledge": true
    },
    "liveAgentSettings": {
      "enableLiveAgent": true
    },
    "workDotComSettings": {
      "enableProfileSkills": true
    },
    "currencySettings": {
      "enableMultiCurrency": true
    },
    "quoteSettings": {
      "enableQuote": true,
      "enableQuotesWithoutOppEnabled": true
    },
    "languageSettings": {
      "enableTranslationWorkbench": true,
      "enableEndUserLanguages": true
    },
    "lightningExperienceSettings": {
      "enableS1DesktopEnabled": true
    }
  }
8
  • The field is mentioned here too. I assume you can see the field under force-app/main/default/objects/Account/fields/ ? Is your source org somehow very old? Does this field contain any useful information on your source org, which means you can't just drop it in your deployment? Commented Apr 29 at 13:43
  • Unfortunately no, it just specifies to track feed history and that is it Commented Apr 30 at 14:57
  • <fields> <fullName>SalesforceCustomer</fullName> <trackFeedHistory>false</trackFeedHistory> </fields> Commented Apr 30 at 14:57
  • it also used in layouts and reports so deployment of those fails Commented Apr 30 at 14:58
  • Can you enable connection finder (help.salesforce.com/…) and deploy
    – Vinay
    Commented May 1 at 16:43

1 Answer 1

2

As mentioned in comments, Enabling Connection Finder in an org and try to re-deployment should fix the issue.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .