Salesforce Known Issues

Data updates are not reflected in UI after a Visualforce+Apex update in Lightning Experience

Apex , VisualForce , Lightning

When data is updated from an Apex controller and redirected to the detail page in Lightning Experience, the updated data is not seen in the UI, even though the data is updated in the database. This is an intermittent behavior and could happen when we are performing the updates continuously and redirecting...

In Review ·Reported By 812 ·Updated 3 days ago

Process builder cannot handle null of cross object on formula criteria

Process Builder does not handle cross-object formula criteria when that relationship field doesn’t have value.

In Review ·Reported By 364 ·Updated 3 days ago

Lightning Component force:showToast event displays toast message behind action window in Lightning Experience and Salesforce1

Mobile , Lightning

When the force:showToast event is fired from a Lightning Component used as an action then the toast message is being displayed behind the action window context. In Lightning Experience the toast is visible behind the transparent background layer that appears with the action window. In Salesforce1...

In Review ·Reported By 358 ·Updated 4 days ago

Spring 19, Report run, height of the row is not automatically adjusted on rich text, looks data cut-off.

Operational Analytics - Reports , Spring 19

Spring 19, Report run, height of the row is not automatically adjusted on rich text, looks data cut-off.

In Review ·Reported By 288 ·Updated Today

Approval Merge Fields Have Wrong Value for Approval Related Emails

Workflow

When using Approval Merge Fields, the values may be incorrect when used as approval related emails (final approval/rejection, immediate email alert). Note: the approval merge fields work correctly in the Approval Assignment Email.

In Review ·Reported By 326 ·Updated 4 days ago

Record page loading error: could not be loaded because it includes too many formula fields with complex formulas, or too many custom fields

Analytics , Mobile , Lightning

This is a Feature Request based on a known limitation around Salesforce1 . Users attempting to load large page layouts may see an error such as: This record could not be loaded because it includes too many formula fields with complex formulas, or too many custom fields. Ask your Salesforce administrator...

In Review ·Reported By 287 ·Updated 4 days ago

"This record was modified by..." your own user message after saving record in custom object related list

Lightning

After updating a related custom object record, the user incorrectly receives an error message (a collision detection) when updating the parent record on the same page. More generically, the error seems to happen any time an entity related to another entity is modified and the ‘Last Modified Date’...

In Review ·Reported By 217 ·Updated 3 days ago

In Lightning, login-as user sometimes redirects back to login page or user page

Lightning

Login-as user is working intermittently. Sometimes login-as logs the administrator out of the org. Other times, login-as redirects the admin back to the user listview or user detail page.

In Review ·Reported By 241 ·Updated 4 days ago

"Invalid component [force:relatedListSingleContainer]" error when deploying a Change Set containing a Case Lightning Page with an Email Related List

Change Sets , Lightning

When deploying a Change Set that contains a Case Lightning Page, if the page contains an Email Related List, deployment will fail with an "Invalid component [force:relatedListSingleContainer]: missing required property [relatedListApiName]" error.

In Review ·Reported By 229 ·Updated 4 days ago

Record Type field is editable in Lightning although the page layout says Read Only

User Interface

Field Accessibility for the Record Type fields is ignored in Lightning. Setting the Opportunity Record Type field to Read Only in the layout works in classic but the field is editable if you change to Lightning.

In Review ·Reported By 214 ·Updated 4 days ago

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