Known Issues · Developer Console
In your Summer '19 Sandbox in Developer Console: if you try to make a change and save a Lightning component which queries the user object and it's fields you will sometimes receive a Field Integrity Exception Error relating to one of the fields being queried. Eg: FIELD_INTEGRITY_EXCEPTION Failed...
Fixed - Summer '19 Patch 5.0 ·Reported By 135 ·Updated 12 days ago
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 188 ·Updated 15 days ago
An exception is thrown when a SOQL query is executed wherein operator IN consists of more than 100 values (mix of integers and decimals) Error message - [object Object]: An unexpected error occurred. Please include this ErrorId if you contact support: 664087795-128954 (838563494)
In Review ·Reported By 4 ·Updated 30 days ago
Unable to update more than one email message record via Dev console / APEX or with Data Loader when the batch size is over 200 When we try to update multiple email message records using the 'open execute anonymous window' in dev console, an error is thrown. The code to update the email messages...
In Review ·Reported By 14 ·Updated 2019-05-20
When building a custom lightning component or app in the developer console, forceChatter:publisher is rendering as an empty container.
In Review ·Reported By 79 ·Updated 2019-05-06
The Enqueued Time in Developer console shows a blank value/ incorrect Day/Month when timezone of the machine is GMT and date format is DD/MM/YYYY. It is a day to month formatting issue and it takes the date from DD/MM/YYYY and shows it as MM/DD/YYYY when the Apex Test Class is run. Example, 01/12/2018...
Fixed - Summer '19 ·Reported By 4 ·Updated 2019-05-04
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,...
Fixed - Spring '19 ·Reported By 4 ·Updated 2019-02-09
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-10-15
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 2018-10-02
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
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.