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 177 ·Updated 2 days ago

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

Scheduled - Spring '19 ·Reported By 62 ·Updated 2 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 28 ·Updated 2 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 13 ·Updated 2 days ago

Sharing locks are not released during Change Set deployment of objects in Master-Detail relationship

Sharing , Change Sets

Some customers may observe that sharing locks are not released after change set deployment or validation of objects in Master-Detail relationship. Attempting to make a sharing-related change hours or even days later generates the following message: "The sharing calculation you requested can't be...

In Review ·Reported By 4 ·Updated 3 days ago

Standard button overridden with VF page disappear from pageLayouts when the SORT ORDER is different (from UI and RETRIEVED METADATA ) is deployed

VisualForce , Metadata , Change Sets

A standard button (New, Edit, View, Delete, and Clone) overridden with a Visualforce page, disappears from pageLayouts (Salesforce Mobile and Lightning Experience Actions" section). When this metadata is retrieved and deployed in another org, standard buttons are not visible in "Salesforce Mobile...

In Review ·Reported By 6 ·Updated 4 days ago

Modifying Deployment Connections hitting timeout error.

Change Sets , Winter 19

When updating a deployment connection, toggling inbound change sets allowed or not, users may encounter a timeout error when attempting to save the changes. The change will go through but, this error will be displayed a few minutes after hitting the save button.

In Review ·Reported By 3 ·Updated 4 days ago

Increased time for deployments after Winter '19 due to long running APEX test classes during validation

Apex , Change Sets , Winter 19

After Winter '19 release a large spike in deployment times are seen. This is due to longer running validation on apex test classes.

Scheduled - Spring '19 ·Reported By 23 ·Updated 5 days ago

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

Filter with invalid operators are allowed to be saved during Entitlement Process creation and causing Bad boolean filter input error when deploy

AppExchange , Packaging , Metadata , Change Sets

- For the Case: Case Record Type Field the supported operators are only "equals to" and "not equals to". All other operators are not allowed. This validation is done when we are validating the Inbound Change list, but is ignored when creating the Entitlement Process. - Actual Result: User is able to...

In Review ·Reported By 15 ·Updated 12 days ago

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