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 574 ·Updated Yesterday

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

Unable to deploy action layout changes (managed action) using sfdx/ant

Metadata , Change Sets

According to this doc mentioned below, we should be able to change actions from a managed package as long as it's the action layout. We are able to change the layout from the org. However the same is not possible using sfdx/ant or workbench. https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/packaging_component_attributes.htm Error...

Scheduled - Summer '21 ·Reported By 1 ·Updated 2 days ago

Unable to upload Macro/Quick Text Folders via change sets.

Change Sets

Some customers may have observed that they see the following error when attempting to upload a changeset containing Macro/Quick Text Folders: Change set: Macro Folder 01 (04tXX000000XXxx) Organization: AW Computing (Production) (00DX0000000XXXX) User: Victor Aaron Gallardo (005X000000XXXxx) Error...

No Fix ·Reported By 7 ·Updated 3 days ago

Row Locks occurring during deployment from Apex Class due to an expired lock set by the Compiler

Apex , Metadata , Eclipse IDE , Change Sets

- User requests might fail with Unable to lock row when deployment/Validation in progress in org even though seeAllData=false in apex test classes. - This is caused by lock set by the compiler.

Fixed - Winter '18 ·Reported By 87 ·Updated 5 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 2 ·Updated 4 days ago

Deploying a change set containing a flow or process builder, creates a new version on the target org while the flow has not been modified.

Change Sets

Deploying a change set containing a flow or process builder, creates a new version on the target org while the flow has not been modified.

Scheduled - Summer '21 ·Reported By 6 ·Updated 5 days ago

Patch org creation fails due to duplicate picklist labels resulting in ISE with Id: -1875811753

AppExchange , Packaging , Metadata , Change Sets

When creating a patch org, the org is created successfully however, the package deploy process fails with an ISE with an Error Id ending in: -1875811753. Picklist values which have the same labels but different API names cannot be deployed and result in an error. This error may be the result of...

In Review ·Reported By 4 ·Updated 5 days ago

Selected values in a record type of custom picklist using Global Value Sets are not deployed correctly through a change set on Event and Task.

Activities , Change Sets

If global value sets are used in a custom picklist field, selected values in a record type is not deployed correctly through a change set on Event and Task object.

In Review ·Reported By 34 ·Updated 8 days ago

Invalid picklist error when deploying the State and Country picklists' Country Code as criteria for a Sharing Rule

Packaging , Change Sets , Summer 19

Users could encounter an error when deploying Sharing Rules that use a Country Code picklist field as sharing criteria via Change Sets or packaging.

In Review ·Reported By 7 ·Updated 11 days ago

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