Known Issues · AppExchange
Packaged GlobalValueSet picklist values not getting updated via Metadata API
In Review ·Reported By 3 ·Updated Today
When you set up data syncing using the instructions provided in the CMA’s setup wizard, the sync fails. This can happen because of an issue with the format of the site URL in the “Set Up Data Syncing” step of the instructions.
In Review ·Reported By 0 ·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
Scheduled - Winter '20 ·Reported By 5 ·Updated 11 days ago
AppExchange customer purchase a listing or update their number of licenses for a specific package, this is not triggering an update on license record in LMO that controls the given package.
Fixed - Spring '19 Patch 20.0 ·Reported By 0 ·Updated 13 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 66 ·Updated 17 days ago
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...
In Review ·Reported By 28 ·Updated 17 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 18 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 18 ·Updated 25 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...
Release In Progress - Summer '19 ·Reported By 6 ·Updated 2019-04-18
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 2019-04-18
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.