The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Fixing common Salesforce Import errors and the surprises that follow a Load (opens in a new tab)

You will learn how to choose between the Data Import Wizard and Data Loader, what the most common import error messages mean and how to fix them, and why duplicate-rule matches and skipped automation can make a successful import look wrong.

Data Import Wizard

  • Runs in the browser from Setup
  • Up to 50,000 records per load
  • Objects the wizard lists in Setup
  • Results in Recent Import Jobs

Data Loader

  • Desktop app, Java 17 or later
  • Up to 150 million with Bulk API 2.0
  • All objects, including Custom Objects
  • Success and error CSV files per run
The Data Import Wizard and Data Loader differ in where they run and how far they scale

The article starts by separating the two import routes. The Data Import Wizard runs in the browser from Setup, suits smaller loads under 50,000 records on supported objects, and is the easier starting point. Data Loader is a desktop application that needs Java 17 or later, covers all objects including Custom Objects, supports upserts, deletes and scheduled command-line loads, and is the route to take when a file outgrows the wizard.

Most failures come from the file rather than the tool. The article walks through the usual causes: a missing required field such as Last Name, values that do not match a picklist exactly, inconsistent date formats, and values longer than the field allows. It explains that duplicate errors can fire against existing Contacts or Accounts because standard matching rules compare names and contact details by similarity, so the record to update may already exist under another Record Type. It also notes that automation can be skipped unless the trigger-workflow option is ticked, and that existing triggers or Validation Rules can reject mixed batches, which a split-by-value approach can work around. Import jobs run from a queue, so admins check Recent Import Jobs and Bulk Data Load Jobs for status and failure reasons, and users should check List Views, ownership and failed rows before re-importing.

The piece also covers fields missing from the mapping list because of page layout or field-level security, the permission needed to import Custom Objects, and the limits of imports, which cannot merge existing duplicates or change matching rules. The closing sections promote the author’s own tools, which the reader should weigh accordingly.

Read the original at dev.to (opens in a new tab)

Worth reading?