Known Issues · Packaging
In Summer'19, while deploying custom object the Default External Access is overriden to "Private" after deploy when "External Sharing Model" is enabled.
Scheduled - Spring '20 ·Reported By 37 ·Updated Yesterday
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...
In Review ·Reported By 3 ·Updated Yesterday
Global Action layouts (quickActions) are not updated when a new 2nd gen Unlocked package version is installed in the target org - Actual Result Global Action layouts are not updated - Expected Result Global Action layouts are updated
In Review ·Reported By 7 ·Updated 2 days ago
Some partners are finding that when they create a patch org, that the patch org will be created but does not successfully work as a patch org. This is due to the package not being deployed to the org due to a discrepancy in enabled features or permissions between the patch org and the packaging developer...
In Review ·Reported By 13 ·Updated 3 days ago
The customer receives the below error when trying to install Package in Summer'18 Orgs. Error: Invalid datasource. Encountered runtime exception in Apex class:
No Fix ·Reported By 4 ·Updated 3 days ago
Page Layout change in 2nd generation unlocked package requires package to be installed twice
In Review ·Reported By 3 ·Updated 3 days ago
Package install fails in winter 20 orgs if it includes a permission set which has access to a standard object record type and the record type is not included in the package.
Fixed - Winter '20 Patch 7.0 ·Reported By 11 ·Updated 5 days ago
If a package upgrade failed and if the second round of the upgrade attempt is done with a different version from the one used in the previous failed upgrade, a compile info of an apex component which has been created at the first upgrade attempt could be used while compiling apex components in the second...
Fixed - Winter '20 ·Reported By 10 ·Updated 5 days ago
Unmanaged Custom Field on Managed Package Object being returned with Namespace when making "Describe" call from Managed code in Subscriber Org. However, when called out from unmanaged code, then it has no Namespace prefix.
In Review ·Reported By 9 ·Updated 5 days ago
Managed Second Generation Package version creation fails if the version has an ancestor and if the metadata has custom metadata type in it or when using ancestor and formula fields
Fixed - Winter '20 ·Reported By 8 ·Updated 5 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.