function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Saul KarlSaul Karl 

Error: Could not resolve standard field's name during ant deployUnpackaged

We try to "ant deployUnpackaged" with the Force.com migration tool for standard objects with custom fields, but it seems that some fields were part of the standard fields some releases ago but now they do not appear in a brand new organization. We are getting the following errors:

objects/Account.object (Account.CurrencyIsoCode) -- Error: Could not resolve standard field's name. (line 313, column 13)

The package.xml looks like:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>*</members>
        <name>CustomObject</name>
    </types>
    <version>34.0</version>
</Package>
 
Saul KarlSaul Karl
I wonder if the CurrencyIsoCode field will appear if we enable multi-currency support in the new organization.
AmrenderAmrender
Hello Karl

You cannot use an asterisk wildcard to work with all standard objects; each standard object must be specified by name. Try below package.xml:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Account</members>
        <name>CustomObject</name>
    </types>
    <version>34.0</version>
</Package>

Regards
Amrender
Anitha KAnitha K
 Hi Karl,

Have you got solution to this issue. now we are facing same issue while deploying custom fields for account object. 

Error : Could not resolve standard field's name.   for the API name Account.ChannelProgramName 

I wonder if the CurrencyIsoCode field will appear if we enable multi-currency support in the new organization. - does this works for you or need any other solution?

Thanks,
Anitha
Sreeni Giddam ReddySreeni Giddam Reddy
Hi Anitha ,
I am also fcing same issue like this  "ERROR running force:package:version:create:  Lead.CurrencyIsoCode: Could not resolve standard field's name.,Contact.CurrencyIsoCode: Could
not resolve standard field's name.,Opportunity.CurrencyIsoCode: Could not resolve standard field's name.,Case.CurrencyIsoCode: Could not resolve standard field's name.,Case.EntitlementId: fullName must end with: __c or __kav or __x or __b or __xo or __e or __p or __mdt,Case.IsStopped: Could not resolve standard field's name.,Case.MilestoneStatus: Could not resolve standard field's name.,Account.CurrencyIsoCode: Could not resolve standard field's name.,Case.MilestoneStatusIcon: Could not resolve standard field's name.,Case.ProductId: fullName must end with: __c or __kav or __x or __b or __xo or __e or __p or __mdt,Case.SlaExitDate: Could not resolve standard field's name.,Case.SlaStartDate: Could not resolve standard field's name.,Case.StopStartDate: Could not resolve standard field's name"

Do you have any idea on this issue please comment .

Regards,
Sreeni.
Sreeni Giddam ReddySreeni Giddam Reddy
Anitha ,

I hope every thing good But you need to enable Multi currencyes in your org. Set up--> Com[pnay information --> enable multi currencyes
if answer is suitable for you pls select as  best answer .

Reagards,
Sreeni..