Known Issues · Eclipse IDE
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 243 ·Updated 4 days ago
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.
Fixed - Winter '18 ·Reported By 87 ·Updated 6 days ago
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 9 ·Updated 25 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...
No Fix ·Reported By 241 ·Updated 2021-01-05
Sharing , Eclipse IDE , Change Sets
You will receive the following email notification when you deploy change of a custom field relationship from Lookup to Master Detail by deployments, such as change sets, Force.com IDE and Force.com Migration Tool. "Your request to change your organization-wide sharing defaults was unsuccessful, please...
In Review ·Reported By 2 ·Updated 2020-11-27
Deploying Entitlement process fail with Fatal error when Milestone entry criteria uses date fields.
Entitlement process with date fields in milestone entry criteria are failing when deployed. Error: Fatal Error
No Fix ·Reported By 3 ·Updated 2020-08-27
<searchLayouts> is not found in OpportunityLineItem.object XML
Packaging , Metadata , Eclipse IDE
On retrieval of the metadata using a tool like ANT or Workbench the <searchLayouts> are not found within OpportunityLineItem.object XML. This causes an issue when you try to deploy the package to another because it will cause the receiving environment to be overwritten after deployment.
No Fix ·Reported By 2 ·Updated 2020-08-14
Metadata , Eclipse IDE , Spring 14 , Change Sets
When using the Ant/ Changeset/ Force.com IDE deploy tools to deploy the System Administrator (Admin) profile into a Spring '14 sandbox/ production, We see this error reported: Error: profiles/Admin.profile(Admin):The user license doesn't allow the permission: CreateWorkBadgeDefinition
In Review ·Reported By 65 ·Updated 2020-08-06
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...
Fixed - Summer '20 ·Reported By 26 ·Updated 2020-07-18
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
Fixed - Summer '20 ·Reported By 2 ·Updated 2020-07-18
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.
