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 346 ·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 Site for a community...

In Review ·Reported By 36 ·Updated 2 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 45 ·Updated 3 days ago

New!Doc Fix: Detail how object level CRUD access is set when a new profile is created or deployed via Change Set

Custom Objects , Metadata , Change Sets

This documentation fix or work item was created to more clearly explain expected default behavior for how object level (CRUD) access is set on deploy of new profiles via change sets. Existing documentation: Special Behavior in Deployments States,...

In Review ·Reported By 0 ·Updated Yesterday

“Re-evaluate Workflow Rules after Field Change” checkbox on the Workflow field update is not deploying correctly using Change sets

Change Sets

Some customers may notice that when they update an existing workflow rule with a changeset, “Re-evaluate Workflow Rules after Field Change” checkbox field on Field Updates is not being updated correctly. The checkbox changes from False to True, but not from True to False when a Field Update is deplo...

In Review ·Reported By 3 ·Updated 3 days ago

Unable to Deploy Field Update on Person Account Record Type

Workflow , Change Sets

When deploying a field update on Person Account Record Types through Change Set and it is failing with error "In field: lookupValue - no RecordType named Account.Record_Type_Name found"

In Review ·Reported By 28 ·Updated 6 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 21 ·Updated 6 days ago

Change set upload fails when it includes Folders of type "Quick Text" or "Macro"

Change Sets

If a change set contains Folders of the type "Quick Text" or "Macro" the upload will fail. An email might contain an error similar to this: xxxxxxxxxx-xxxxx (885809063) Currently folders of these types are not support by change sets.

Scheduled - Winter '20 ·Reported By 3 ·Updated 6 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 49 ·Updated 7 days ago

Duplicate Rule with FilterLogic cannot be deployed with change sets

Change Sets

Duplicate Rule with Filter Logic cannot be deployed with change sets and other MAPI deployments.

In Review ·Reported By 30 ·Updated 8 days ago

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