This article explains how to bulk import Custom Object records, including create, update, deduplication logic, bulk action controls, and import error handling.

Overview

You can bulk create and update Custom Object records via CSV import.

The import supports:

• Creating new Custom Object records

• Updating existing Custom Object records

• Create + Update in a single import

• Importing Owner and Follower fields

• Deduplication using Record ID or a selected Unique Field

• Full bulk action monitoring with pause/resume/cancel support

Creating Custom Object Records

To create a new Custom Object record:

• Only the Primary Field is mandatory.

• No other field is required to create a record.

If no Record ID or matching unique field is found, a new record will be created.

Updating Custom Object Records

To update an existing Custom Object record:

• Only Record ID can be used to directly update a record.

• No other field can override Record ID for update.

If Record ID exists:

• The system will find and update that exact record.

• No duplicate matching logic will apply.

Create + Update Behavior

If both create and update are enabled in a single import:

• If Record ID exists → Update that record.

• If Record ID does not exist → Create a new record.

Unique Field Deduplication Logic

If your Custom Object has multiple unique fields, and you map more than one during import:

You must select which unique field to use for deduplication.

Example:

Let:

• UF1 = Unique Field 1

• UF2 = Unique Field 2

  User selects UF1 for deduplication.

Important

• Only one unique field can be selected for dedupe.

• If other mapped unique fields conflict, the row will fail with an error.

• The system will not auto-resolve multi-unique conflicts.

Update Rules for Empty Values

The “Update Empty Values” setting applies during update.

However:

• “Update to Empty” is NOT allowed for:

  • Primary field

  • Required fields

If attempted:

• The row will fail with an error.

Multi-Object Import Limitation

Currently:

• Only one Custom Object can be imported at a time.

• All other objects will be disabled once a Custom Object is selected.

Tooltip message:

“Multiple objects import with Custom Objects coming soon”

Bulk Actions Page (Custom Objects)

A dedicated Bulk Actions page exists for Custom Objects, similar to Opportunities.

Available Actions During Import

While an import is in progress, you can:

• Pause

• Resume

• Cancel

These controls apply only while the bulk action is running.

Bulk Action Details View

Each import has a detail page showing:

• Bulk Action ID

• Type (Create / Update / Create + Update)

• Name of the Import

• Date Created

• Status

• Initiated By

Bulk Actions Filters

You can filter bulk imports by:

• Date

• Status

• Users

Import Statistics Modal

Each import has a Stats Modal with the following tabs:

1. All

Shows one row for every line in the CSV file.

2. Success

Shows one row for every successfully imported line.

3. Error

Shows one row for every failed line.

4. Warnings

Shows one row for every warning generated.

Stats Modal Columns

Each row includes:

• Line No

• Record ID

• Object Primary Field

• Status

Possible statuses:

• Success

• Error

• Warning (only on Warnings tab)

For Error and Warning tabs, two additional columns appear:

• Error/Warning Message

• How to Resolve

Error and Warning Behavior

All validation messages follow the same standards used for:

• Contact Imports

• Opportunity Imports

This includes:

• Required field validation

• Unique constraint violations

• Invalid owner assignment

• Invalid data formats

• Restricted field update attempts

• Duplicate detection failures

Errors block record creation/update.

Warnings allow processing but flag data issues.

Common Scenarios

1. Record ID Provided and Exists → Record updated.

2. Record ID Provided and Does Not Exist → New record created.

3. Unique Field Selected and Duplicate Found → Record updated (if no other unique conflict).

4. Multiple Unique Conflicts → Row fails with error.

5. Required Field Cleared Using “Update to Empty” → Row fails with error.

Best Practices

• Always map Record ID if you intend to update.

• Use only one unique field for deduplication.

• Review required fields before enabling “Update Empty.”

• Check the Error tab after every import.

• Use Pause if you detect mapping issues mid-import.