Salesforce Known Issues

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 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 180 ·Updated 4 days ago

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 23 ·Updated 3 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 204 ·Updated 11 days ago

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.

In Review ·Reported By 27 ·Updated 13 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 7 ·Updated 18 days ago

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

In Review ·Reported By 5 ·Updated 2019-03-19

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 13 ·Updated 2019-02-27

Error: profiles/Admin.profile(Admin):The user license doesn't allow the permission: CreateWorkBadgeDefinition

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 61 ·Updated 2019-02-25

Error deploying Compact Layouts - In field: RecordTypeId - no CustomField named Account.RecordTypeId found

Metadata , Eclipse IDE , Change Sets

When deploying object metadata including Compact layouts to an Org without an existing record type for that object in the destination Org (but that is included with the object as part of the deploy), It fails with the below error - objects/Account.object (Account.Account_Compact_Layout) -- Error:...

Fixed - Spring '19 ·Reported By 69 ·Updated 2019-02-09

Parsing an inline query referring to the User.Account foreign key fails with the "Didn't understand relationship 'Account' in field path..." error

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 2019-02-09

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