Error: Could not resolve standard field’s name. This error means that a source salesforce org had enabled some features which was not enabled or unavailable in a destination org. You have to discover the official documentation for object field description.
Table of Contents
How to resolve “could not resolve standard field’s name” error?
Account.object (Account.DunsNumber): Error: Could not resolve standard field’s name. Use a target org with the same features and licenses as your source org. Exclude these files from your deployment if you don’t need them. Check that none of your feature licenses have expired. Features must be the same on both orgs.
How can I Fix my Org shape in Salesforce DX?
If the quick fix didn’t help, try one of the following solutions to fix this issue: Spin up a scratch org with Salesforce DX. If you are familiar with Salesforce DX, you can customize the sfdx-project.json to match the shape of your source org.
Why does my Salesforce deployment fail during deployment?
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. 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.
Why are some standard components not available in my Org?
Some standard components only appear in an org when a related feature is enabled. We often see this with Data.com, Multi-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.
What is Salesforce consultant?
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.
When do standard components only appear in an org?
Some standard components only appear in an org when a related feature is enabled. We often see this with Data.com, Multi-Currency, or Person Accounts.
How to fix a syslog?
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.
How to check if a feature license is enabled?
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.
How to match production licenses in Sandbox?
In the sandbox, from Setup, enter Company Information in the Quick Find box, then select Company Information, and click Match Production Licenses.
Can you customize Salesforce DX?
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.
Can you update entitlements without refreshing the 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.