Known Issues · Change Sets
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 607 ·Updated Yesterday
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 98 ·Updated Yesterday
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 39 ·Updated 2 days ago
MDAPI does not retrieve custom picklists values for the Record Types from Contact object as part of Person Account.
In Review ·Reported By 27 ·Updated 2 days ago
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 53 ·Updated 6 days ago
Duplicate Rule with Filter Logic cannot be deployed with change sets and other MAPI deployments.
In Review ·Reported By 118 ·Updated 7 days ago
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 71 ·Updated 7 days ago
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 3 ·Updated 7 days ago
"Data Not Available" error when adding components to Outbound Change Set. The issue happens when a report which is used on the page layout of a custom object, is moved to a private folder.
In Review ·Reported By 0 ·Updated 7 days ago
- When customer deploy updating more than 18 Omni queues in a bulk update, a gack is thrown, preventing the update. - Customer validation passes but deploy fails with error stack trace error code: 1792645791
In Review ·Reported By 7 ·Updated 8 days ago
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.