Salesforce Known Issues

Known Issues · Change Sets

"Invalid component [force:relatedListSingleContainer]" error when deploying a Change Set containing a Case Lightning Page with an Email Related List

Change Sets , Lightning

When deploying a Change Set that contains a Case Lightning Page, if the page contains an Email Related List, deployment will fail with an "Invalid component [force:relatedListSingleContainer]: missing required property [relatedListApiName]" error.

In Review ·Reported By 229 ·Updated 4 days ago

Duplicate case team entry error on deploy of case assignment rules

Change Sets

Some customers have observed that they encounter the following error when deploying case assignment rules in their target org. “Duplicate case team entry for XXXXX” XXXXX here is the name of the Predefined Case Team on the case assignment rule being deployed.

In Review ·Reported By 45 ·Updated 3 days ago

Process flow consisting of a chatter action "Post to Chatter" throws an error when deployed via change sets

Change Sets , Flow

Some customers have observed their process flow that was created/updated via a deployed change set throws the following error when the conditions for the flow are met: “The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301XXXXXXXXXXX....

In Review ·Reported By 38 ·Updated 3 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

Deploying Account and Contact OWD in the same deployment package may fail

Change Sets , Spring 17

Deploying Account and Contact OWD in the same deployment package may fail with message as " Deployment error: ReadWrite is not a valid sharing model for Contact when Account sharing model is Private"

In Review ·Reported By 15 ·Updated 5 days ago

Deploying change set containing community fails with error: "An unknown exception has occurred"

AppExchange , Change Sets , Communities

This issue occurs when deploying a community from an org to another using change sets. Typically the error thrown when validating the change set in the target org is "An unknown exception has occurred." Below is a technical explanation of how this issue occurs. When a Force.com Site for a community...

In Review ·Reported By 25 ·Updated 6 days ago

SOQL "FOR VIEW" behaves differently when an test is executed for a Change Set Validation versus a Force.com Migration Deployment Validation

Apex , Change Sets

1) when Apex tests are executed for Change Set Validations, the Most Recently used (MRU) is disabled. 2) when Apex tests are executed for Force.com Migration Tool Deployment validations, the MRU is enabled.

No Fix ·Reported By 2 ·Updated 6 days ago

Error: "Not in package.xml" when attempting to validate or deploy a Change Set.

Packaging , Partner , Change Sets

Users may notice an error message "Not in package.xml" when attempting to validate or deploy an inbound Change Set. --- When a Developer deletes a component from their package, the component continues to exist in the subscriber org even after the package is upgraded. When the component is...

In Review ·Reported By 10 ·Updated 9 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

Cannot update record type translations via Metadata API if the translated record type is a package member

API , Metadata , Change Sets

Cannot update record type translations via Metadata API if the translated record type is a package member.

In Review ·Reported By 4 ·Updated 18 days ago

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