Salesforce Known Issues

Known Issues · Data Loader

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 716 ·Updated 2018-08-15

Block Large Data Export policy condition in Transaction Security is not working when NumberOfRows >500

API , Platform , Data Export , Data Loader

When trying to implement the example provided by this link, to stop users from downloading 2000+ records via the API. It does not work as expected. https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_interface_TxnSecurity_PolicyCondition.htm

Fixed - Summer '18 Patch 9.0 ·Reported By 6 ·Updated 2018-06-16

[Data Loader] - [Mac] Path to default configuration is incorrect if not installed in /Applications

Data Loader

The Data Loader application needs to be located in /Applications in order to work. If installed then not placed in /Applications, you will receive an error when opening the Data Loader: Please make sure that the config file: /Volumes/Data Loader/Data Loader.app/Contents/Resources/conf/config.properties...

Fixed ·Reported By 60 ·Updated 2018-05-09

Query on KnowledgeableUser doesn't return results or all expected records

API , Chatter , Data Export , Data Loader , Communities

Users may report that they are not getting any results or all expected results when querying the KnowledgeableUser entity via the API. KnowledgeableUser https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_knowledgeableuser.htm For example, you may a Topic in your...

Fixed - Spring '18 Patch 17.0 ·Reported By 1 ·Updated 2018-04-20

ContentNote with 4 characters inserted through API displays incorrectly in lightning note editor

API , Content and Files , Data Loader , Lightning

ContentNote records inserted via the API using Data Loader for example, with Content mapped to a .txt file containing 4 characters is inserted successfully however, when viewing the resulting note record in lightning experience's note editor, the body or Note details display unexpected characters and...

No Fix ·Reported By 3 ·Updated 2018-04-09

Incorrect OldValue and NewValue exported with the Dataloader from history tables for year end dates

Data Loader

When exporting the OldValue and NewValue fields on a history table, if the fields contain dates of 12/30/xxxx or 12/31/xxxx, the dates returned will be one year later. For example, a date of 12/30/2018 would be exported as 12/30/2019.

In Review ·Reported By 2 ·Updated 2018-04-02

Creating Opportunities with Primary Campaign Source from some contacts results in Internal Salesforce Error

Campaigns , Sales and Marketing , Data Loader , Spring 18

Creating Opportunities with Primary Campaign Source from some contacts results in Internal Salesforce Error. one of the Error ID: 1834803483-30153 (-1121570161) This is due to bad data at campaign member (Duplicates).

Fixed ·Reported By 30 ·Updated 2018-02-22

SOQL queries of ContentDownloadURL on ContentDistribution intermittently return an invalid path

Content and Files , Data Loader

Intermittently, querying the ContentDownloadURL field on ContentDistribution will return a URL that contains "papers" in the path. For example, the URL will begin with: https://na35.content.force.com/sfc/dist/papers/version/download/... A URL returned this way will not error when used. A valid...

Fixed - Spring '18 Patch 6.3 ·Reported By 0 ·Updated 2018-01-31

Data Loader Version 41 is not available for download from Winter '18 orgs.

Data Loader , Winter 18

Winter '18 orgs are still pointing to version 40 of the Data Loader. Due to this customers cannot access API version 41. The release notes state: "All Resources Updated to API Version 41.0" http://releasenotes.docs.salesforce.com/en-us/winter18/release-notes/rn_api_ui_version.htm But...

Fixed ·Reported By 6 ·Updated 2018-01-17

Logging cases through the Help & Training Portal on instances with TLS 1.0 disabled

API , Mobile , Performance , Platform , Authentication , Data Loader , Email Clients , Outlook

On July 22, 2017, we disabled TLS 1.0 security encryption on the AP0, AP2, AP3, NA2, NA44, NA45, NA60, NA87, and CS19 instances. A subset of users attempting to login via browsers that are not compliant with TLS 1.1 or higher may not have the ability to log a case through the Help & Training portal.

No Fix ·Reported By 2 ·Updated 2018-01-15

Prev | 11 to 20 of 43 | 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.