Known Issues · Eclipse IDE
Row Locks occurring during deployment from Apex Class due to an expired lock set by the Compiler
Apex , Metadata , Eclipse IDE , Change Sets
- User requests might fail with Unable to lock row when deployment/Validation in progress in org even though seeAllData=false in apex test classes. - This is caused by lock set by the compiler.
In Review ·Reported By 70 ·Updated 6 days ago
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 may or may not contain reference fields. Example error: FATAL_ERROR System.UnexpectedException: Opportunity: bad field names on insert/update call: Account NOTE : If the fields are not updatable...
In Review ·Reported By 236 ·Updated 12 days ago
Apex , AppExchange , Packaging , Metadata , User Interface , Eclipse IDE , Change Sets
Metadata deployments via change sets or packages may show that the deployment was successful without any error messages. However, upon checking - the expected components are not actually deployed or present in the target org. This may occur if your change set contains Apex and requires the deploy...
Release In Progress - Summer '20 ·Reported By 26 ·Updated 20 days ago
Error: Property is referenced by visualforce page during deployment
Metadata , Eclipse IDE , Change Sets
Remove the property from the controller and remove it's reference from VF page then deploy the VF page and controller together - it throw below error during deployment. Error: "The property Boolean XXXXXXX is referenced by Visualforce Page (ELA_Checklist) in salesforce.com. Remove the usage and try...
In Review ·Reported By 236 ·Updated 2020-06-10
Apex , Eclipse IDE , Change Sets , Spring 16
Compiling an apex class which refers to the User.Account foreign key in an inline query fails with the ApiQueryException exception, "Didn't understand relationship 'Account' in field path...", if some class which refers to some foreign key in User and whose API version is 31.0 or prior has been compiled...
Fixed - Spring '19 ·Reported By 16 ·Updated 2020-05-28
Analytics , Metadata , Eclipse IDE
The issue is that errors seen while submitting translations for CRT labels may be misleading when section names are duplicated in report types or column names are duplicated in translations that refer to report types. The error message(s) may not point to the right report type or the right section and...
In Review ·Reported By 8 ·Updated 2020-05-14
CustomObjectTranslation Metadata API retrieved XML mismatches with the Metadata WSDL
API , Metadata , Eclipse IDE
XML returned by Metadata API for LookupFilterTranslation does not validate against the WSDL because it does not always include the errorMessage & informationalMessage elements.
No Fix ·Reported By 3 ·Updated 2020-04-14
Translation Labels are saved to incorrect page layout sections if there are duplicate section names
API , Metadata , Eclipse IDE
Deploying translated labels for page layout section is saved to incorrect section in presence of layout sections with duplicate names.
No Fix ·Reported By 17 ·Updated 2020-04-06
Error when deploying list view with My Team's Opportunities
Apex , Eclipse IDE , Change Sets , Salesforce DX , Winter 20
Error when deploying list view with My Team's Opportunities from Winter '20 and getting an error. [Failed]: Update of ListView Opportunity.My_Team_s_Open_Opportunities: Error on line 1938, col 16: Invalid scope:Team, requires opportunity team selling enabled
Release In Progress - Summer '20 ·Reported By 2 ·Updated 2020-01-13
Custom Metadata Type cannot be deployed if it has validation rules
Custom Objects , Metadata , Eclipse IDE , Change Sets
Custom Metadata Type cannot be deployed if it has validation rules.
In Review ·Reported By 25 ·Updated 2019-12-13
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.
