Salesforce Known Issues
Trailblazer Community

Duplicate rule validation blocks update during ‘Check for New Data’

using the "Check for New Data" button (part of D&B optimizer) to update account records. If the update causes the record to match another account via duplicate/match rule, then the validation blocks the account update with the following error. 'This record wasn't updated by the D&B Account Optimization...

In Review ·Reported By 9 ·Updated 11 days ago

Geocoder for San Marino does not provide latitude and longitude. Works when country is changed to Italy

According to the coverage document, coverage for San Marino is House Number, Street level – Full coverage to house number level. Second highest level of coverage. However, latitude and longitude are always 0 for ...

In Review ·Reported By 1 ·Updated 2021-05-31

Get More Accounts - GACK when button clicked from Lightning Experience has identified an issue related to the "Get More Accounts" button not functioning as expected when State and Country Picklists are enabled.

Fixed - Spring '17 Patch 14.0 ·Reported By 5 ·Updated 2021-05-26 - Assessment application causing developers deployment issues has identified an edge case where the 'Native' assessment application is causing managed package updates to fail. Failure occurs when deploying updates from one org having the assessment application active to a target org without the application.

Fixed - Spring '17 ·Reported By 1 ·Updated 2021-05-26

Duplicate Social Parent Key records causes Full sandbox copy to stall.

Sandbox ,

Duplicate Social Parent keys in a production organization can cause a Full sandbox copy to stall when they are copied due to uniqueness constraints. One known cause was due to issues during Lead conversion where the parent record was not updated correctly.

Fixed - Winter '16 ·Reported By 1 ·Updated 2021-05-26

Records are not being geocoded

Users may have noticed that some records created on February 1st were not geocoded.

In Review ·Reported By 7 ·Updated 2021-03-11

Updating the record via "Check for new data" as standard user should not require "View setup and configuration"

Updating the record via "Check for New Data" button on Account requires system permission "View Setup and Configuration.

Fixed - Spring '21 Patch 7.0 ·Reported By 6 ·Updated 2021-02-18

Updates showing in Account/Lead History even when fields were unchanged on record

When blocking an update from the automated updates by the Clean User, DI Rule (specifically Company Info in this case) show in the Account/Lead History and Chatter (if enabled) as if the fields were updated, but the fields are untouched on the record.

No Fix ·Reported By 0 ·Updated 2020-06-05

Internal Server Error with Duplicate Matching rule filtering encrypted fields

Sales and Marketing ,

The customer may report that when use Platform Encryption & Duplicate Management with encrypted custom field, it generates the internal server error (example below). Error ID: 1552025370-12478 (983828907)

In Review ·Reported By 19 ·Updated 2020-04-02 Clean jobs get 'hung up' and may not process all records

Organizations may observe inconsistent behavior with Clean jobs while using the DUNSRight matching where not all records are being processed, leaving many in the 'Not Compared' clean status.

No Fix ·Reported By 1 ·Updated 2020-01-03

1 to 10 of 33 | 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.