Known Issues · Summer 16
In Review ·Reported By 55 ·Updated 8 days ago
When the URL decoded value of startURL contains a relative path with white spaces 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.
In Review ·Reported By 3 ·Updated 8 days ago
When using a SOSL query that uses an OFFSET clause in Apex, the results are ordered by ID. The same query run via the API (for instance from the Query Editor view in the Developer Console) will return the results sorted by relevance.
Fixed - Summer '18 Patch 5.0 ·Reported By 23 ·Updated 10 days ago
For some organizations the Sharing Criteria rules list when adding components to a change set will display duplicates. This can cause the error "Package member already exists" if both items attempt to be added to the change set.
In Review ·Reported By 56 ·Updated 11 days ago
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 15 ·Updated 12 days ago
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 4 ·Updated 20 days ago
Edits to User records that trigger a rounding or padding operation on Geolocation custom fields could fail to trigger flows.
No Fix ·Reported By 12 ·Updated 27 days ago
In Spring 16, non-admin users with profile permission "Deploy Change Sets” were able to validate and deploy change sets. However, in Summer 16, non-admin users with profile permissions "Deploy Change Sets” attempting to validate or deploy change set doesn't work.
In Review ·Reported By 7 ·Updated 2018-05-17
Users are receiving an ISE when attempting to access Transaction Security. An internal server error has occurred An error has occurred while processing your request. The salesforce.com support team has been notified of the problem. If you believe you have additional information that may be of help...
Fixed - Spring '17 Patch 2.0 ·Reported By 0 ·Updated 2018-05-17
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 11 ·Updated 2018-05-07
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.