Known Issues · VisualForce

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 305 ·Updated Yesterday

Custom Buttons for VisualForce pages set to "Display in New Window" should open in a New Window

VisualForce

[Lighting Experience] Custom Buttons for VisualForce pages set to "Display in New Window" open within the same tab. Expected: The custom button for a VisualForce page should open in a new window.

In Review ·Reported By 129 ·Updated Yesterday

Receiving Error when querying for lookup fields while using sObject.recalculateFormulas() method.

Apex , API , VisualForce , Eclipse IDE , Developer Console , Winter 16

Exception occurs when sObject.recalculateFormulas() is called and the query which retrieves the object contains reference fields. Example error: FATAL_ERROR System.UnexpectedException: Opportunity: bad field names on insert/update call: Account NOTE : If the fields are not updatable and they are...

In Review ·Reported By 145 ·Updated 3 days ago

Salesforce1 - Scrolling on standard record Create/Edit pages locks up when coming from Visualforce on iOS devices

Mobile , VisualForce

Users may experience inconsistent scrolling behavior on standard record Create and Edit pages when coming from a Visualforce page in Salesforce1. The page may lock up not allowing any scrolling for periods of time and then begin working as expected again. This is occurring in both the downloadable...

In Review ·Reported By 17 ·Updated 2 days ago

Collision Detection is triggered when editing unread Leads from LEX and Salesforce1

Mobile , Platform , VisualForce

You may receive the following error when trying to edit unread Leads from the Lightning Experience or Salesforce1 UIs: "This record was modified by (the user updating the Lead) during your edit session. Make a note of the data you entered, then reload the record and enter your updates again." This...

In Review ·Reported By 32 ·Updated 3 days ago

Under LEX, apex:outputLink redirects to classic view, instead of Lightning view

VisualForce , Summer 17 , Lightning

From Summer 17, Under Lightning Experience, The links created using <apex:outputLink> tag redirect to classic view instead of lightning view. But in Spring 17, This redirects to the lightning view.

In Review ·Reported By 10 ·Updated 3 days ago

Salesforce1 shows "Sorry to Interrupt" error when navigating to Object Home pages from Visualforce with navigateToURL or navigateToObjectHome on iPads

Mobile , VisualForce , Spring 17

Users may see a "Sorry to Interrupt" error when using custom Visualforce pages that navigate to Object Home pages (shows recently accessed records and List Views for the object). This has only been reported and confirmed on iPad devices where there are multiple navigation calls done to the Object Home...

In Review ·Reported By 7 ·Updated 4 days ago

The filter which still has ambiguous NOT/AND or NOT/OR should not be allowed to be saved.

VisualForce , User Interface

The filter which still has ambiguous NOT/AND or NOT/OR should not be allowed to be saved. For instance, "- "NOT (1) AND 2 " - "NOT 1 AND 2"

Scheduled - Summer '18 ·Reported By 0 ·Updated 5 days ago

Deployment of VF component fails with "Unsupported attribute" error

Packaging , VisualForce , Metadata , Eclipse IDE , Change Set , Change Sets

A deployment of visualforce components fails with an error: "Unsupported attribute myAttribute in <c:myComponent> in myVfPage at line 369 column 50"

In Review ·Reported By 42 ·Updated 6 days ago

Salesforce1 standard back navigation button responds only if tapped twice when using Visualforce pages

Mobile , VisualForce

Under certain scenarios the standard Salesforce1 back navigation button will only respond if tapped twice. This occurs when the programmatic calls like window.history.back() and sforce.one.back() are used to navigate back one page first, and then the user attempts to use the standard back button to go...

In Review ·Reported By 6 ·Updated 8 days ago

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