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 504 ·Updated 2 days ago
- 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 24 ·Updated 2 days ago
Creating HTML editor components with "HTML Comment Tags" on community pages (example : <!-- html comments -->) is causing the issue on deployment.
Release In Progress - Summer '20 Patch 8.0 ·Reported By 4 ·Updated 4 days ago
Some customers may have observed that they see the following error when attempting to deploy a changeset with Community Themes: Community Site.com 0 0 We couldn't validate componentAttributes in Community/themes/partnerCentral.json for component 0f3fb8c1-d37c-4681-9038-21b567169927. Error: attribute...
Scheduled - Winter '21 ·Reported By 3 ·Updated 4 days ago
Unable to update the quick action layout on the change set.
In Review ·Reported By 0 ·Updated 4 days ago
Attempts to deploy the standard LogACall quick action through a managed package, unmanaged package, or change set will fail. The error message displayed will vary depending on the type of deployment: As an installation of a managed package: An unexpected error occurred. Please include this...
In Review ·Reported By 15 ·Updated 5 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 70 ·Updated 6 days ago
We have a problem for the transaction management on the deployment for Lightning Web Components in Change Sets. It is causing a fatal error internally and therefore the Change Set is stuck in progress for days.
In Review ·Reported By 4 ·Updated 11 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 57 ·Updated 12 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 18 ·Updated 12 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.