Known Issues · Sales and Marketing
For the latest information on this issue, please read our root cause update: https://help.salesforce.com/articleView?id=000320234&type=1&mode=1 What’s the issue? On May 17, 2019, Salesforce blocked access to certain instances after an incident involving broader permissions being applied to users...
In Review ·Reported By 1451 ·Updated Yesterday
When confetti is enabled in path settings, it is not shown to users without "View Setup and Configuration" permissions.
In Review ·Reported By 85 ·Updated Yesterday
Opportunity Record in Lightning is not reflecting the update made by Process Builder written based on "Opportunity Team" object.
In Review ·Reported By 4 ·Updated 2 days ago
Leads may stop coming into Salesforce via LinkedIn Lead Gen even though the Member has the necessary permissions set within their LinkedIn Account. This typically occurs when a single LinkedIn Account is being used for multiple environments.
In Review ·Reported By 2 ·Updated 2 days ago
When the Contract Name field gets exposed to users via Field-Level Security (FLS), hovering over the ‘Related To’ field that relates a Task to a Contract results in the displayed value fluctuating between Contract Number and the value of the Contract Name field. After a time, or when opening a New...
In Review ·Reported By 1 ·Updated 2 days ago
If an organization has the 'Account Name' field added to the 'Influenced Opportunities' related list (on the Campaigns entity), that related list will fail to populate after Campaign Influence records are added to the Opportunity.
In Review ·Reported By 7 ·Updated 8 days ago
The fields Sales Price and Quantity are editable in LEX for the Product Line Items that has a Schedule. These fields are not editable in classic.
No Fix ·Reported By 12 ·Updated 9 days ago
Not all existing Opportunities for the Account are visible when converting Lead to an existing Account and trying to attach to existing Opportunity.
In Review ·Reported By 0 ·Updated 9 days ago
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 17 ·Updated 12 days ago
When using Aloha(classic) view in Salesforce and attempt to trigger a milestone that is based off field criteria change criteria, such as BEGINS( OwnerId , "005"), or Status = Option A, the milestone is not created
In Review ·Reported By 2 ·Updated 13 days ago
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.