Known Issues · Metadata
Unexpected validation rule executes while installing managed package with customer metadata due to customer package created with parent-child relationships between the custom metadata types. Package also contain validation rules for all child objects and validating on parent object attributes (parent...
In Review ·Reported By 29 ·Updated 2 days ago
Deploying a process Builder which references a group by Id, instead of name under in-vocable actions like Send Custom Notification, can cause errors. Even though the flows deploy successfully, customer may be observing errors on firing a process builder, having in-vocable actions like Custom Notification,...
In Review ·Reported By 5 ·Updated Yesterday
Calling Formula.recalculateFormulas() from Apex containing formula field with custom metadata type is throwing UnexpectedException below: System.UnexpectedException: Salesforce System Error: 489632835-45620 (-848256302)
In Review ·Reported By 4 ·Updated Today
Deploying ExperienceBundle with Custom Theme Layout fails
Scheduled - Spring '21 ·Reported By 4 ·Updated 2 days ago
Error deploying Lightning Web Components to Winter '21 Orgs
Scheduled - Winter '21 Patch 7.0 ·Reported By 1 ·Updated 2 days ago
When trying to push the standard value set for ContractStatus results in a error "force-app\main\default\standardValueSets\ContractStatus.standardValueSet-meta.xml Field: null is not a picklist"
In Review ·Reported By 108 ·Updated 5 days ago
Values for audit fields (Createdby, LastModifiedby, CreatedDate and LastModifiedDate) are returned incorrect when retrieved using List Metadata feature in Metadata API
In Review ·Reported By 6 ·Updated 4 days ago
2GP Managed Package version creation fails when using Ancestry and Roll-up summary field
Scheduled - Spring '21 ·Reported By 3 ·Updated 4 days ago
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 1 ·Updated 4 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.