Bulk API gets error "MISSING_ARGUMENT:fiedXXX__c not specified:--" when using "N/A#"
Last updated 2016-07-28 ·Reference W-2268502 ·Reported By 10 users
Trying to use the documented way to set a field value to null using bulk API by passing “#N/A” as the field value, however, this is not working when the field is an external ID for a related object. For example, if Account has a lookup field into a custom object, and that custom object has an external Id, the bulk API allows you to specify the related object’s external ID to link the Account to the custom object, but if you specity “#N/A” to clear the field, the upsert fails with "MISSING_ARGUMENT:fiedXXX__c not specified:--" error.
For example. If you have a lookup field in Account that points to a custom object called SuperAccount. In SuperAccount you have an external ID that you want to use when upserting records into Account and you want to clear it.
The CSV looks like this:
"Account_External_ID__c", "Name", "SuperAccount"
"Acme1", "Acme 1 updated", "#N/A"
And the fields are mapped as follows:
"Account_External_ID__c" → "Account_External_ID__c"
“Name” → “Name”
"SuperAccount" → “Super_Account__r.external_ID__c"
You will receive the error.
No workaround available. Please use the synchronous API instead.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.