Known Issues · AppExchange
Several customers have observed that they are seeing longer than usual delays with change sets, this currently affects ALL instances. This also affects Packaging so customers might see a Package Not Found error when attempting to upgrade/install a package from the appexchange. Customers may have...
Fixed - Spring '19 Patch 13.1 ·Reported By 201 ·Updated 4 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 22 ·Updated Today
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 3 ·Updated Yesterday
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 1 ·Updated Today
Some customers may get package failure issue if the package contains inactive record types. The error is displayed on UI: 1. (ObjectName__c.RecordtypeName) This record type cannot be deactivated because it is the last active record type for RecordtypeLabel ObjectName__c.RecordtypeName: This record...
Scheduled - Summer '19 ·Reported By 1 ·Updated Yesterday
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
In Review ·Reported By 5 ·Updated 2 days ago
There are certain package orgs in which the push upgrade history pages time out due to the size of the error logs. The pages have a specific view size limit in which R&D is investigating and working on a tentative solution.
Fixed - Spring '19 Patch 13.0 ·Reported By 0 ·Updated 4 days ago
This issue occurs when a search is done in the subscriber org tab of a License Management App and there are many orgs listed. Ex. List of 50+ pages of subscriber orgs. When the search is performed on the same org name, erased and searched it again the results are inconsistent.
In Review ·Reported By 0 ·Updated 6 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 17 ·Updated 8 days ago
This issue occurs when a Trialsource org has communities set up and has a template assigned. A template is created afterward and the org created from the template does not have the template assigned.
In Review ·Reported By 1 ·Updated 10 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.