Quick Fix: Could not resolve standard field's name

The Salesforce API returns error messages when it can’t deploy metadata. Learn more about the error, what the cause is and how you can fix the problem.

If you see this Salesforce error message:

  • Account.object (Account.DunsNumber): Error: Could not resolve standard field’s name.

Try this quick fix:

  1. Use a target org with the same features and licenses as your source org.

  2. Exclude these files from your deployment if you don’t need them.

  3. Check that none of your feature licenses have expired.

Features must be the same on both orgs.

Some standard components only appear in an org when a related feature is enabled. We often see this with Data.comMulti-Currency, or Person Accounts.

Depending on the feature, it may be possible to turn it on for free in Setup, or you may need to pay an extra free and contact Salesforce support to enable it. If only one org has the feature and it is not enabled on the other org, the different standard fields and standard objects will cause this error during deployment.

Feature Affected Components
Data.com Account.DunsNumber
Data.com Clean Account.CleanStatus
Multi-Currency Account.CurrencyIsoCode
Person Accounts Account.PersonAssistantName
Advanced Calendaring
(or by using Salesforce for Outlook)        

Consider this example: As a Salesforce consultant, you work on a new customer project. Your customer pays the extra licensing fee for Data.com, which is enabled in their production org and in their sandboxes. But their sandbox quota is maxed out, so you create a free Developer Edition org yourself. Because it’s a Developer Edition org, it doesn’t have the same features and fields like Account.DunsNumber and Account.NaicsCode will be missing. When you deploy from production to your developer org, it won’t work.

Other Solutions

Try one of the following solutions to fix this issue.

Spin up a custom Salesforce DX scratch org.

If you are familiar with Salesforce DX, you can customize the sfdx-project.json to match the shape of your source org. If you want an automatic solution, you can manage your scratch orgs through Blue Canvas and we’ll detect the right configuration automatically.

License counts and quotas in Salesforce Setup

License counts and quotas in Salesforce Setup

Check the status of your licenses in Setup.

If you want to check which feature licenses are enabled in your orgs, you can look them up. From Setup, enter Company Information in the Quick Find box, then select Company Information. Review the list of licenses and check that it is the same on both orgs. Verify the expiration dates–a license may be expired and the Status shows Disabled or Renewal. Contact Salesforce if that’s the case.

Create a new Developer Sandbox.

Sandboxes inherit the feature configuration from their parent environment. Try deploying from your source org into a sandbox instead of a different edition.

Update the license info in your sandbox.

If you already use a sandbox and you recently added new licenses in production, there’s a way you can update the entitlements without refreshing the sandbox. This way you can enable the feature but you won’t loose undeployed changes.

In the sandbox, from Setup, enter Company Information in the Quick Find box, then select Company Information, and click Match Production Licenses.

Blue Canvas can automate your deployments.

Our app automatically handles issues like this. Our unique deployment engine talks directly to Salesforce and knows how to work around errors like this one and many others. With Blue Canvas, your deployments can be quick and simple, so you deploy in seconds not hours.

Ready to learn more? Schedule a personalized demo with one of our deployment experts now.