Known Issues · Packaging
Salesforce transactions that are creating or modifying binary data type fields, also known as BLOBs, and subsequently perform rollback operations either implicitly (Apex test method completion) or explicitly (manual savepoint capture and rollback) may encounter errors attempting to access those fields...
In Review ·Reported By 38 ·Updated 2 days ago
The user in the org where the package is installed can customize selected fields on a compact layout. This user should not be able to update it. If they customize it then the package upgrade will remove the select fields and return to default.
In Review ·Reported By 25 ·Updated 3 days ago
Translation workbench settings in managed package is not included into a patch correctly, when creating a patch from a main development org,
In Review ·Reported By 10 ·Updated 3 days ago
Custom Object exists in Managed Package, and customer create a new layout for that custom object. In this case, even if customer use the correct fullname, customer cannot get the value using Metadata.Operations.retrieve This Custom Objects is package members, so It has Namespace. and the customer's...
Scheduled - Summer '19 Patch 2.0 ·Reported By 3 ·Updated 3 days ago
This issue periodically occurs when deleting a managed custom button in the package org and it still shows up in the Edit Search Layout. The button is not found to be hard deleted and still show up as an option to select in the associated object.
Scheduled - Winter '20 ·Reported By 0 ·Updated 3 days ago
This issue occurs when packaged components are associated with a community in an org. This typically happens when there are LEX components or aura bundles are used in a community. References are created in the backend and its difficult to remove these unless the user reviews all the pages in the com...
Scheduled - Summer '19 ·Reported By 6 ·Updated 4 days ago
Package subscribers are able to delete reports that are referenced in Lightning Pages which causes package upgrades to fail.
In Review ·Reported By 4 ·Updated 4 days ago
Following Error message appears when uploading a package ERROR MESSAGE: An unexpected error occurred. Please include this ErrorId if you contact support: 1014169018-81141 (1327239692) ORA-30006: resource busy; acquire with WAIT timeout expired ORA-06512: at "SNEEZY.CMETAACCESS", line 579 ORA-06512:...
In Review ·Reported By 0 ·Updated 5 days ago
Some partners may observe that when they create a new Trial org from the TSO org they are not able to upload any files to the Trial org with the default System Admin user. Please note that this only affects the default system admin user, subsequent admin users that are created manually after the Trial...
Scheduled - Summer '19 ·Reported By 3 ·Updated 6 days ago
Package installation is failing with the error: "This app can't be installed. There are problems that prevent this package from being installed. An unexpected error occurred. Please include this ErrorId if you contact support: 940194413-34580 (-1818293276)" The complete ErrorId might be different...
In Review ·Reported By 2 ·Updated 6 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.