Known Issues · Change Sets
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...
Release In Progress - Spring '20 ·Reported By 56 ·Updated 4 days ago
Duplicate Rule with Filter Logic cannot be deployed with change sets and other MAPI deployments.
In Review ·Reported By 41 ·Updated 6 days ago
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 443 ·Updated 10 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 39 ·Updated 10 days ago
When there is a delete operation, or an operation on a soft-deleted field (Field1), in a deployment package with another field (Field2) being updated and dependent on Field1, the deployment will fail with errors observed against Field2 similar to the following: Error: An unexpected error occurred. Please...
Release In Progress - Spring '20 Patch 3.0 ·Reported By 18 ·Updated 10 days ago
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 56 ·Updated 13 days ago
Error when deploying list view with My Team's Opportunities from Winter '20 and getting an error. [Failed]: Update of ListView Opportunity.My_Team_s_Open_Opportunities: Error on line 1938, col 16: Invalid scope:Team, requires opportunity team selling enabled
Scheduled - Summer '20 ·Reported By 2 ·Updated 14 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 49 ·Updated 18 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 1 ·Updated 19 days ago
- 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.
In Review ·Reported By 45 ·Updated 20 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.