# Upsert Salesforce Data
**Upsert** is a combination of Updating and Inserting. If a record in a file matches an existing record, the existing record is updated with the values in your file. The record is created as a new entity if no match is found.
**Limitation on Record ID Availability**\
Except for the **Upsert** operation in a single DataLoader job, when errors occur during data operations, Salesforce imposes a limitation where **record ID information is not available** in the error details.
The following articles describe using **Single DataLoader** to upsert data into Salesforce via a CSV file.
1. Log in to your ARM account.
2. Hover your mouse over the **`DataLoader`** module and select **`DataLoader`**.
3. Click **`Upsert`** on the right side of the screen.
4. Choose your **`Salesforce Org`** and your org environment (**`Production or Development Edition`**, **`Sandbox`**, or **`Pre-Release`**).
5. The corresponding **`URL`** and your **`Username`** are automatically generated based on the above selection.
6. Click **`Login and Fetch Objects`**.
7. Select the object you wish to upsert data into (e.g., **`Account`**, **`Contact`**, **`Lead`**). Use the **`search`** function and **`filter`** button for convenience.
8. Click **`Next`**.
9. Upload your CSV file by clicking the **`Upload`** button.
10. Click **`OK`** on the notification popup showing impacted records.
11. Prepare field mappings: Match CSV columns to Salesforce fields.
12. Use **`Automap`** to match fields automatically if names align.
13. Confirm all required fields are mapped, then click **`Next`**.
### Process Summary Options
* **Name:** Assign a name to the job.
* **Category:** Organize processes by categories (create new or use existing).
* **External ID Field:** Specify unique identifier other than Salesforce ID (e.g., ERP ID).
* **Object:** Displays the object being upserted.
* **Operation Type:** Displays **Upsert**.
* **Impacted Records:** Shows record count.
You can also schedule tasks as **Daily**, **Weekly**, or **On-demand**. Click **`Save`** to store and run later.
14. The task appears in the **DataLoader Summary** list.
15. Click **`Run`** to execute the task immediately.
### DataLoader Configuration Options
| Configuration | Description |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Batch Size** |
Salesforce Batch API is based on SOAP principles and is optimized for real-time client applications that update small numbers of records at a time. Although SOAP API can also process large numbers of records, it becomes less practical when the data sets contain hundreds of thousands of records. In those cases, Bulk API is the best option. Batch API processes data in smaller batches than Bulk API, resulting in a higher API call usage per operation on large volumes of data.
Note:When you run a Bulk API job, processing more batches in parallel means giving that job a higher degree of parallelism, giving your overall run better data throughput.
|
| **Disable workflow rules** | Deactivates workflows during operation and reactivates post-process. |
| **Disable Validation Rules** | Deactivates validation rules during the process and re-enables afterward. |
| **Insert/Update with null values** | Allows null value updates in destination org. |
| **Use UTF-8 file encoding** | Required for data containing English alphabets. Disable for non-English content. |
22. Click **`Run`** to begin.
### Results Monitoring
* **Results of Last Run:** Shows success/failure record count dynamically.
* **Records:** Displays the total records affected.
### More Options
1. **Edit:** Update job configuration.
2. **Abort:** Stop a running job.
3. **Schedule:** Set periodic execution.
4. **Delete:** Remove the job.
5. **Log:** View execution logs.
6. **VR/WFR:** View validation/workflow rules. See [Validation/ Workflow Rules](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/dataloader/validation-workflow-rules).
7. **Clone:** Create a copy of the process with an option to choose a different data file.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/dataloader/single-dataloader/upsert-salesforce-data.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
