Salesforce Known Issues
Trailblazer Community

Known Issues · Data Loader

Entity History Created Date is not being set properly for custom objects

Custom Objects , Data Loader

When specifying the created date via an Insert call with the Data Loader for a custom object with "create audit field record" permission enabled, the custom object record has the expected created date but the History related list will show the date of the import instead of the value specified in the...

In Review ·Reported By 1 ·Updated 4 days ago

Data Loader OAuth login may fail when using saved usernames and Server host setting is changed unexpectedly

Data Loader , Sandbox

When attempting to login using Data Loader's OAuth option, users encounter a generic error: Please check your username and password. If you still can't log in, contact your Salesforce administrator. And no login attempt may be present or recorded in the user record's login history. In addition,...

In Review ·Reported By 30 ·Updated 5 days ago

Custom campaign influence records are not deleted when an associated campaign is deleted.

Campaigns , Data Loader

Custom campaign influence records are not deleted when an associated campaign is deleted. This blocks further changes to related opportunity records.

Fixed ·Reported By 0 ·Updated 27 days ago

The import wizard fails with a generic error.

Data Loader

Some customers using the import wizard may encounter difficulty importing one or more files even though all of the data is correctly formatted and all required fields are present.

In Review ·Reported By 726 ·Updated 30 days ago

Quotes Sync is adding decimal places and changing the Unit Price on Quote Line Items

API , Data Loader

When inserting a Quote Line Item record via API(Data Loader, Apex), it adds additional decimal places during quote sync. This occurs when Multi-Currency is enabled and the decimal place is set to 4.

In Review ·Reported By 1 ·Updated 2020-06-09

Empty Bulk Dataloader result file (success/failure ) if the batch status is completed but with error message. (i.e. batch exceeds 10 mins timeout.)

Data Loader

When using Apex dataloader to load data and if a batch hit any error (e.g: batch exceeds 10 mins timeout.), the process.success and failure files are empty. This issue happens when BULK api is used.

In Review ·Reported By 28 ·Updated 2020-06-05

New is not a standard action and cannot be overridden for DocumentChecklistItem object error

Data Loader , Metadata , Winter 20 , Spring 20

If you try to retrieve/deploy DocumentChecklistItem object on a spring20 org(v. 224) you may receive this error message: "New is not a standard action and cannot be overridden for DocumentChecklistItem object", with a package.xml similar to the following. <?xml version="1.0" encoding="UTF-8"?> <Package...

Fixed - Summer '20 Patch 2.0 ·Reported By 1 ·Updated 2020-05-30

18-Character ID not being considered insensitive when performing data update from API

API , Data Loader

18-Character ID not being considered insensitive when performing data update from API (I.e: workbench). According to the document below, 18-Character IDs should be considered insensitive. https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/field_types.htm?search_text=Field%20Types "TSome...

Fixed - Spring '20 Patch 14.0 ·Reported By 1 ·Updated 2020-04-06

With Dataloader, incorrect rows displayed in the Success file when an Insert fails with a "Failed to parse date" error

Data Loader

When inserting records using the Dataloader, if rows fail to insert due to a "Failed to parse date" error, then in the Success file that's generated, the error rows will be displayed as successes, and the preceding rows will not be included in the Success files. This only occurs when using the Bulk ...

No Fix ·Reported By 2 ·Updated 2020-03-02

Data Loader v45 for Windows installer fails to create desktop icon when user installing has a non-standard desktop path

Data Loader

When OneDrive is syncing the user's desktop or the user has a non-standard desktop path the installer for Data Loader v45 (for Windows) will fail when attempting to create the desktop icon.

In Review ·Reported By 12 ·Updated 2020-02-05

1 to 10 of 52 | Next

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.