This article explains how to determine which Salesforce Data Loader actions (create, update, delete, query) are available for a specific Salesforce standard object, and which fields in that object support each action.
Salesforce Data Loader uses the SOAP API (Simple Object Access Protocol) to create, retrieve, update, and delete records in standard and custom objects.
The functionality available for each object is documented in the SOAP API Developer Guide on the Salesforce Developers site. While the guide provides detailed information about working with the SOAP API, it can also be used to determine the types of actions available for each object when using Data Loader.
From the Developer Guide, click Reference and then Standard Objects on the left. Select the object you are working with, such as Opportunity.
The Supported Calls section lists the actions that can be performed on the object.
The actions most commonly used in Data Loader are:
create() – Indicates whether Data Loader can insert new records into the object.
delete() – Indicates whether Data Loader can delete records from the object.
query() – Indicates whether Data Loader can export records from the object.
update() – Indicates whether Data Loader can update records in the object.
For example, the Opportunity object supports all four actions.
Some data is stored in child or junction objects. For example, Opportunity status history is stored in the OpportunityHistory object. The only Data Loader action available for OpportunityHistory is query(), which means records can be exported but cannot be created, updated, or deleted.
Review the Supported Calls section for each object to determine the actions available.
See also: API Call Basics
The Fields section lists the fields that can be accessed for the object. Each field includes the API name, field type, and available properties.
Common field properties include:
Create – Indicates that Data Loader can populate the field when creating a record.
Filter – Indicates that the field can be used as a filter when exporting records.
Nillable – Indicates that Data Loader can clear the field value.
Update – Indicates that Data Loader can modify the field value.
For example, you can filter Opportunity exports by AccountId when the field supports filtering.
The field description may also contain additional information, such as API version requirements or usage considerations.
System fields are not included in the Fields section because Salesforce populates them automatically. However, users with the Set Audit Fields upon Record Creation permission may be able to populate certain system fields during record creation.
By reviewing both the Supported Calls and Fields sections in the SOAP API Developer Guide for a standard object, you can determine exactly which Data Loader operations are supported for that object and what actions can be performed on its individual fields.
For custom objects, refer to the Custom Objects reference documentation. For a UI-based alternative to explore object metadata and API functionality without writing code, use Workbench.
See also:
Custom Objects
Workbench
000384062

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.