Known Issues · Summer 16
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 45 ·Updated Yesterday
In Review ·Reported By 18 ·Updated Today
Customer has a form inside a lightning community template. When viewing the form as System Administrator - the values get populated as expected. However, when viewing the same form as a community user, the values are not populated properly. This happens only on custom fields, the standard fields are...
In Review ·Reported By 4 ·Updated 4 days ago
When a Lightning Page contains both a Custom Lightning Component AND a Custom Visualforce Component, users without the "View Setup and Configuration" system permission may be unable to access the page.
In Review ·Reported By 40 ·Updated 10 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 28 days ago
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 10 ·Updated 2018-01-20
If Historical Trending is enabled (see https://help.salesforce.com/articleView?id=reports_historical_setup.htm&type=0 for instructions) for a given sObject (i.e. Opportunity, Case, etc.), and a lookup field is tracked by this feature, when a SOQL query on the historical data entity (i.e. Opportunity__hd)...
Fixed - Spring '17 Patch 18.0 ·Reported By 0 ·Updated 2018-01-18
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.
In Review ·Reported By 4 ·Updated 2018-01-17
In Review ·Reported By 51 ·Updated 2018-01-15
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.