Known Issues · Developer Console

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.

In Review ·Reported By 64 ·Updated Yesterday

New!Storefront Toolkit is incompatible with CDATA

Developer Console , Commerce Cloud API/OCAPI

Currently, both old and new Storefront Toolkit may work incorrectly or stop working entirely when a CDATA section is used in the html code of the storefront (most commonly generated from isml).

In Review ·Reported By 0 ·Updated Today

Querying for a record using several fields fails/When performing an import a duplicate error message is produced, but the Id doesn't return a record

API , Data Loader , Developer Console , Data Import Wizard

After a bulk import fails, the records that were not able to be imported may still exist in a queriable table, even though those record do not exist within the org. This can cause issues when attempting to perform queries using multiple fields, as those fields do not exist on the queriable table,...

Scheduled - Spring '19 ·Reported By 3 ·Updated 6 days ago

data:soql:query reports "no results" when limits of Big Objects are encountered

Developer Console

When querying big objects and running into limits, the API reports back totalSize=-1 when it actually returns lots of query results.

In Review ·Reported By 1 ·Updated 2018-08-15

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 164 ·Updated 2018-07-23

Summer'18 - ISE Error trying to access Developer Console or Create a Debug log

Apex , Developer Console

When the cumulative size of debug logs in an org is much greater than 250 MB, there is an existing issue calculating the total size, resulting in errors being presented to the user in the Developer Console and Setup menu. As mentioned in the Summer ’18 Release Notes (https://releasenotes.docs.salesforce.com/en-us/summer18/release-notes/rn_forcecom_debugging_log_limits.htm)...

Fixed - Summer '18 Patch 5.0 ·Reported By 6 ·Updated 2018-06-09

Query on ContentVersion returns 0 results immediately after querying ContentDocumentLink.

Apex , Developer Console

Querying ContentDocumentLink then ContentVersion (for a large amount of files), the ContentVersion query fails and returns 0. Similarly, if you do some other query between ContentDocumentLink and ContentVersion, the ContentVersion query succeeds

Fixed - Summer '18 ·Reported By 2 ·Updated 2018-05-05

SOQL query returns different value than is on UI for formula fields

Developer Console

SOQL query returns different value than is on UI for formula fields when the field used in the formula is blank.

In Review ·Reported By 14 ·Updated 2018-03-20

Winter'18 - Parent Relationship query on DuplicateRecordSet fails

Sandbox , Developer Console , Winter 18

SOQL on DuplicateRecordSet like : "Select DuplicateRule.MasterLabel from DuplicateRecordSet" Get this error: INVALID_FIELD: Select DuplicateRule.MasterLabel from DuplicateRecordSet ^ ERROR at Row:1:Column:8 No such column 'MasterLabel' on entity 'Name'. If you are attempting to use a custom...

Fixed - Spring '18 ·Reported By 2 ·Updated 2018-02-10

The Address field are no longer allowed in order by clause in Soql query (After Spring 18 )

Apex , Developer Console , Spring 18

Some customers using the Address field in order by clause in Soql query see the below error: "BillingAddress field can not be sorted in a query call".

Fixed - Spring '18 Patch 5.0 ·Reported By 13 ·Updated 2018-01-23

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