Account fields available in default scratch org but not in regular dev org

Question

I am pushing Metadata from a (namespaced) scratch org with that definition

{
  "orgName": "my_DEV",
  "country": "US",
  "edition": "Developer",
  "language": "en_US",
  "hasSampleData": true,
  "features": [],
  "settings": {
    "orgPreferenceSettings": {
      "s1DesktopEnabled": true,
      "chatterEnabled": true
    }
  }
}

into a packaging org using this SFDX command

sfdx force:source:deploy -p ./sfdx-source/appw  -l RunLocalTests -w 15 -u mydev

It fails as Account is missing many fields that it has in the scratch org.

sfdx-source/appw/main/default/objects/Account/fields/CleanStatus.field-meta.xml Could not resolve standard field's name. (266:13) sfdx-source/appw/main/default/objects/Account/fields/OperatingHoursId.field-meta.xml fullName must end with: __c or __kav or __x or __b or __xo or __e or __p or __mdt (312:13) sfdx-source/appw/main/default/flexipages/AccountRecordPage.flexipage-meta.xml Your org doesn't have access to component runtime_sales_social:socialPanel.

Looks like I am missing:

1. Account.CleanStatus
2. Account.OperatingHoursId
3. runtime_sales_social:socialPanel Component

When I google this it looks like Data.com Clean fields which I never activly activated. How can I get rid of those fields.

Answer 1

"Regular" (Developer Edition) scratch orgs don't have the same feature set as Enterprise Edition orgs, or any arbitrary org. Packaging orgs often have a lot of features turned off, as well, to avoid inadvertent dependencies.

That makes pulling Profile metadata out of a scratch org for deployment to a non-scratch org... difficult, in many cases, and Data.com is a common culprit in my experience.

Here, though, it looks like you just have the actual field metadata for a number of standard fields, which are part of the Data.com feature that's enabled by default in Developer Edition scratch orgs. You probably don't want that metadata in your source tree at all, since it's not part of your package, and I'm surprised it got pulled in the first place. I'd simply delete all of the standard field metadata.

I don't know what feature the runtime_sales_social:socialPanel component is part of off the top of my head. If that's something you intended to include in your package you'll have to identify the feature and activate it in the packaging org to allow deployment.