When using Salesforce Bulk API 2.0 to ingest (upload) records, you can retrieve the results of a completed job — both successfully processed records and failed records — by calling specific API endpoints.
However, you may notice that the field values in the returned results appear as blank strings even though those same fields were populated in the original CSV file provided during the job upload.
This issue occurs when retrieving job results from the following Bulk API 2.0 endpoints:
/services/data/vXX.X/jobs/ingest/jobID/successfulResults//services/data/vXX.X/jobs/ingest/jobID/failedResults/The records are created or updated successfully in Salesforce (the operation itself does not fail), but the field values in the results response appear as empty strings instead of the expected values from the original CSV.
This issue occurs when the field names in the CSV file header do not exactly match the Salesforce object's Field API names in terms of case sensitivity.
Bulk API 2.0 uses the CSV column headers to map data to Salesforce fields. Salesforce Field API names are case-sensitive in this context. If the column header in your CSV file uses a different case than the official Field API name — for example, using name instead of Name, or description instead of Description — Bulk API 2.0 may still process the record create or update operation without throwing an error. However, when you retrieve the job results, the API cannot match the original column header to the field, and returns an empty string for that field in the results response.
Review your CSV file and compare each column header name against the Field API names for the Salesforce object you are loading data into. Ensure that the column headers in the CSV exactly match the Field API names, including capitalization.
For example:
Name (not name or NAME)Description (not description)Custom_Field__c (not custom_field__c)
After correcting the column headers in the CSV file, re-upload the job. The job results should then return the correct field values in the success and failure result responses.
000380583

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.