SFDX force:source:push command fails on History Tracking

Spring 18 , Winter 18

When History Tracking is enabled in a scratch Org on a standard object and/or standard field that metadata change is not pulled down with a force:source:pull. Result is that History tracking changes cannot be pushed to another Scratch Org.

In Review ·Reported By 91 ·Updated Yesterday

Unable to update lightning:inputField of type lookup to empty value (null), when using it in lightning:recordEditForm

Spring 18 , Lightning

When we use lightning:inputField of type lookup in a lightning:recordEditForm and try to update it to null by clearing the existing value, we can see that the value is not updated and the previous value persists.

In Review ·Reported By 28 ·Updated Today

Lookup dialog boxes on Visualforce pages with lightningstylesheets = true are still styled as classic

VisualForce , Spring 18 , Lightning

if a VF page embedded in LEX has lightningstylesheets = true, clicking on the lookup icon in the page, opens the lookup dialog box in classic

In Review ·Reported By 26 ·Updated Today

Adding an image to Knowledge Article in Lightning using existing Salesforce Files doesn't set appropriate visibility

Content and Files , Service , Knowledge , Spring 18 , Lightning

This Known Issue (KI) is a continuation of the previous one here: Images added to a Rich Text Area field on a Knowledge Article created in Lightning are visible only to the creator https://success.salesforce.com/issues_view?id=a1p3A000000mCiTQAU Reference: W-4428041 With Spring '18 the KI above...

In Review ·Reported By 13 ·Updated Yesterday

"The source organization of this sandbox has been deleted. We are using your production organization to update the sandbox." when refreshing a clone.

Sandbox , Spring 18

The error "The source organization of this sandbox has been deleted. We are using your production organization to update the sandbox." is thrown when attempting to refresh a cloned sandbox when the source sandbox is on the release preview and production is on a different release. It is expected behavior...

In Review ·Reported By 6 ·Updated Today

Refreshing a lead record in lightning does not load the custom component with a visibility criteria set even when the criteria is met

Spring 18 , Lightning

When a Lightning Component is included in a record's Lightning App Builder page and its visibility is controlled using - Set Component Visibility, the component loads successfully when the record is accessed from the list view for the first time (initial load). However, upon subsequent reload of the...

In Review ·Reported By 2 ·Updated Yesterday

Spring18 - Lightning - Scroll bar is displayed at Dashboard Component in Home tab.

Analytics , Spring 18 , Lightning

In Spring18, Scroll bar is displayed at dashboard component in Home tab. This issue only occurs on IE11 and Chrome browser.

In Review ·Reported By 64 ·Updated 4 days ago

"Related list - Single" is showing spinner forever where are many related list singles that aren't in the page layout.

Spring 18 , Lightning

When we add multiple Related list - Single and choose objects that are not in page layout then the page just keep spinning.

In Review ·Reported By 10 ·Updated 4 days ago

<lightning:recordForm> not capturing validation errors in Component's controller

Apex , Spring 18 , Lightning

When you define a custom validation defined on an object & use <lightning:recordForm> in lightning component, you will notice the validation errors doesn't get captured in the components helper class even though the error displays on the User Interface.

In Review ·Reported By 9 ·Updated 5 days ago

Metadata cannot be pulled after first authentication with Lightning for GMail

Metadata , Spring 18

Some customers have observed that after the first authentication of a user in Lightning for Email, the following error is thrown when pulling metadata using the Salesforce CLI. ERROR: Entity of type 'AuthProvider' named 'Lightning For Gmail' cannot be found.

In Review ·Reported By 1 ·Updated 7 days ago

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