Salesforce Known Issues

Known Issues · Eclipse IDE

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

Scheduled - Summer '20 ·Reported By 2 ·Updated 14 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.

In Review ·Reported By 45 ·Updated 20 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 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 211 ·Updated 21 days ago

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.

In Review ·Reported By 16 ·Updated 24 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 229 ·Updated 2019-12-20

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

Metadata deployments (change sets or package) show successful without error message but the expected components are not deployed

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...

In Review ·Reported By 24 ·Updated 2019-12-12

Deployment error when deploying sharing rules together with queues on the same package

Packaging , Metadata , Eclipse IDE

When deploying sharing rules and queues together the following error can occurr error: "sharedFrom not allowed:queue - [QueueName]", when using ANT or the IDE.

No Fix ·Reported By 44 ·Updated 2019-11-07

Internal Server Error when retrieving all 'StandardValueSetTranslation' or describe call on StandardValueSetTranslation

API , Metadata , Eclipse IDE

Sometimes while using ListMetaData or describe call on StandardValueSetTranslation Users might face Internal Server Error or UNKNOWN_EXCEPTION . Sample Error message for Describe Call UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 635387088-4851...

In Review ·Reported By 10 ·Updated 2019-10-16

Managed second generation package version creation fails when using ancestry and formula fields/custom metadata type

AppExchange , Packaging , Metadata , Eclipse IDE , Change Sets , Salesforce DX

Managed Second Generation Package version creation fails if the version has an ancestor and if the metadata has custom metadata type in it or when using ancestor and formula fields

Fixed - Winter '20 ·Reported By 8 ·Updated 2019-10-12

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