Known Issues · Summer 16
Dashboard can't facet on SAQL widget when the org has Namespace enabled. Autofilter is not working either with SAQL widgets in orgs with a Namespace enabled.
No Fix ·Reported By 4 ·Updated 3 days ago
In Review ·Reported By 25 ·Updated 2021-01-27
If an object with multiple record types have it's 'New' button overridden by a VF page then we see that the CSS for record selection page in lightning experience is different than in Salesforce classic.
No Fix ·Reported By 18 ·Updated 2020-12-24
Trial org created through a template will have incorrect FLS settings if FLS and page layout settings are different
In Review ·Reported By 5 ·Updated 2020-12-15
When using a custom "Log a Call" Quick Action on Cases, the "[Person] logged a call" Feed Item is not generated if a Process Builder flow updates the generated task. When saving, you will notice that you receive a message that lets you know it was successful, the Chatter Feed refreshes and the Feed...
In Review ·Reported By 30 ·Updated 2020-12-14
When the URL decoded value of startURL contains a relative path with white spaces or invalid characters (e.g. éá) before the first existing question mark, "Bad_Start_Url, startURL was not a relative path or contained invalid characters" is thrown when redirected to the auth provider servlet.
Fixed - Winter '21 ·Reported By 11 ·Updated 2020-10-19
Under certain conditions a custom Lightning or Visualforce page may not scroll after a user interacts with input fields on Android devices in the Salesforce1 mobile application. Typically this occurs only when the input field isn't initially visible on the page, requiring the user to scroll down...
In Review ·Reported By 39 ·Updated 2020-09-23
Edits to User records that trigger a rounding or padding operation on Geolocation custom fields could fail to trigger flows.
In Review ·Reported By 15 ·Updated 2020-06-17
In Review ·Reported By 7 ·Updated 2020-03-10
Since Summer'16, the following code in Lightning Component doesn't work expectedly. The "v.date1" is defined as Date type and is expected to be cleared as well as Spring'16. ----- component.set("v.date1", ""); -----
In Review ·Reported By 5 ·Updated 2019-01-28
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.