Salesforce Known Issues
Trailblazer Community

VisualForce Page reference id not working on Lightning

Apex , Communities , Winter 17 , Lightning

Parameters are no longer collected in lightning vf pages using the following method. Map<String,String> params = ApexPages.currentPage().getParameters(); currentAccountId = (Id)params.get('id');

In Review ·Reported By 37 ·Updated 3 days ago

Unable to copy text in LEX

Performance , Winter 17

Users using LEX with Chrome version 54 may experience issues selecting text on their records. As the users are unable to select the text they will not be able to copy and paste, however edit a record will allow you to select and copy the details.

In Review ·Reported By 88 ·Updated 2022-08-16

VF page containing <wave:dashboard> displays an error in IE11 when embedded into a standard page layout.

Analytics , Winter 17

Embedding a VF page which contains <wave:dashboard> into a standard page layout displays a 'cannot be displayed in frame' error in IE 11. Firefox does not show any error but the Wave Dashboard does not appear. Chrome browser successfully displays embedded VF pages with Wave Dashboards.

Fixed - Spring '17 Patch 3.0 ·Reported By 7 ·Updated 2022-07-28

Test.setCreatedDate() on CaseComment record results in InvalidParameterValueException

Apex , API , Winter 17

Test.setCreatedDate() in a Test Class results in the following error during Run Test when it is used with CaseComment Object : System.InvalidParameterValueException: Provide the ID of a test-context sObject as the first parameter for setCreatedDate().

In Review ·Reported By 14 ·Updated 2022-02-15

OData4j is expecting the JSON query response to have metadata and properties in order

Winter 17

For OData2, OData4j is expecting the Json query response to have metadata first, then properties. This is not documented in the OData spec, but causing failure of query if the order is reversed. Specifically, the customers should respond the following query with Json as below: (metadata first, then...

In Review ·Reported By 6 ·Updated 2022-02-15

Users cannot type '@' in fields with Norwegian keyboard in the Lightning Experience for Winter '17

User Interface , Winter 17

Users cannot type '@' in fields with Norwegian keyboard in the Lightning Experience for Winter '17 for users on a windows operating system.

In Review ·Reported By 5 ·Updated 2022-02-15

External Lookup field renders as external id in Salesforce Classic List Views

Platform , Winter 17

External lookup fields show id instead of Name in list views in Salesforce Classic. Valid External Lookups should render the Name of the external object not the id. This is only an issue in Salesforce Classic.

In Review ·Reported By 1 ·Updated 2022-02-15

forceChatter:publisher renders empty when used in a custom lightning component

Developer Console , Winter 17 , Lightning

When building a custom lightning component or app in the developer console, forceChatter:publisher is rendering as an empty container.

Fixed - Summer '17 ·Reported By 130 ·Updated 2022-02-10

The Inbound change sets are not accessible for newly uploaded change sets from Spring 17 to Winter 17 org.

Metadata , Change Sets , Winter 17 , Spring 17

After Spring 17 , the newly created change sets which when moved from spring 17 orgs to an winter 17 org . The inbound change sets pages are not accessible and giving an ISE like: Error ID: 87452590-127216 (2080591907)

Fixed - Spring '17 Patch 3.2 ·Reported By 86 ·Updated 2022-02-10

Navigating tabs in Lightning on a Patch org throws error "Managed Package Patch Modification Exception:"

AppExchange , Winter 17

Navigating tabs in lightning on a Patch org throws error "Managed Package Patch Modification Exception:" - Actual Result When opening custom object tab, an error dialog is shown - Expected Result When opening custom object tab, it opens without errors

Fixed - Winter '19 Patch 4.0 ·Reported By 26 ·Updated 2022-02-10

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