Salesforce Known Issues
Trailblazer Community

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 643 ·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 83 ·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 55 ·Updated Today

User receives Organization Administration locked error when trying to view Deployment Status or the Change Set in progress when validating.

Change Sets , Spring 21

Some customers may have observed that they see the following error when they start a change set validation Organization Administration Locked The changes you requested require to temporarily lock your organization's administration setup. However, the administration setup has already...

In Review ·Reported By 4 ·Updated Yesterday

When we select to deploy processes and flows as active and set the test coverage to 0%, test classes not related to the flow/process are running.

Metadata , Change Sets , Flow , Process Builder

In the process automation setting, When you set "Deploy processes and flows as active" to enabled and Specify a minimum test coverage percentage for flows to 0% and try to deploy my process and/or flow, we observe that the apex test classes not related to the process or flow are running.

In Review ·Reported By 4 ·Updated 2 days ago

Dashboard Component's attributes displayUnits, and maxValuesDisplayed can't be retrieved or deployed when component type is FlexTable

Metadata , Change Sets

When deploying LEX dashboard via ChangeSet or MetadataAPI, [Display Units] and [Max Groups Displayed] of Dashboard Component are not copied. This issue only occurs when componentType is Lightning Table.

In Review ·Reported By 3 ·Updated 2 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 123 ·Updated 9 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 32 ·Updated 10 days ago

Standard action:PrepareForBilling is missing from OrderItem page layout in Summer 21 release

Change Sets , Summer 21

Some customers may have observed they are seeing the following error when trying to deploy custom OrderItem object Page layout from Spring' 21 org to Summer' 21 org: Error Message: "In field: excludeButtons, no such standard action:PrepareForBilling" This occurs due to the following XML tag being...

In Review ·Reported By 17 ·Updated 10 days ago

List View deployment failing with the error "Value too long for field: Name maximum length is:40"

API , Metadata , Change Sets , Listviews

Standard lists have a 40 characters limit for their Name/Label. Because of translation features, the standard list's metadata XML might be created with a long translation and then cause the error "Value too long for field: Name maximum length is:40" on deployment.

In Review ·Reported By 4 ·Updated 10 days ago

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