Known Issues · Packaging
The customer is unable to deploy page layout changes through post install script when the script is run as part of package deployment. - Actual Result Throwing a NoAccessException in the background. - Expected Result The install script should run fine and update the layout.
In Review ·Reported By 9 ·Updated Yesterday
Push Upgrade is failing with an error number and the message: "Component [force:relatedListSingleContainer] attribute [relatedListApiName]: Could not find related list [AttachedContentDocuments]"
In Review ·Reported By 8 ·Updated Yesterday
There is currently an issue with Trial Orgs missing the installed package components when created from a Trial Source org. The package will be installed but there will be no components listed underneath. This poses a problem since an error will occur when upgrading the package in the Trial org since...
In Review ·Reported By 15 ·Updated 2 days ago
A deployment of visualforce components fails with an error: "Unsupported attribute myAttribute in <c:myComponent> in myVfPage at line 369 column 50"
Fixed - Winter '19 ·Reported By 68 ·Updated 4 days ago
When deploying sharing rules and queues together the following error can occurr error: "sharedFrom not allowed:queue - [QueueName]", when using ANT or the IDE.
In Review ·Reported By 19 ·Updated 3 days ago
This issue occurs in different variations but a snippet of the error appears below a majority of the time: Unable to retrieve value INVALID_TYPE: sObject type 'PackageBooleanValue' is not supported. Class.FCRM.FCR_FMASupport. --- The error can occur by sending an email from a case to saving...
Fixed - Winter '19 Patch 5.0 ·Reported By 22 ·Updated 4 days ago
Testing the values of feature parameters outside of their namespace in places like the dev console is giving error in winter 19 as well as inside their own namespace. System.FeatureManagement.checkPackageBooleanValue('testnamespace__parametername')); System.NoAccessException: The System namespace...
Fixed - Winter '19 Patch 7.0 ·Reported By 11 ·Updated 4 days ago
Some customers may get error when upgrading a package: (LightningPageName) Component [desktopDashboards:embeddedDashboard] attribute [dashboardName]: Invalid dashboard Unique Name DashboardName - no dashboards found.
Fixed - Winter '19 Patch 8.0 ·Reported By 3 ·Updated 4 days ago
If an Apex Class or a Trigger reference AboutMe, FullPhotoURL or SmallPhotoURL fields in User object, Chatter object will be listed as an Organization-level Feature Dependencies. Due to this, if a package contain these Apex Class or Trigger and installed it to Chatter turned off org, installation...
Fixed - Winter '19 ·Reported By 3 ·Updated 4 days ago
Package install fails in winter 19 orgs if it contains pick list which includes consecutive whitespaces in picklist values. No issue installing in summer 18 orgs.
Fixed - Winter '19 Patch 4.0 ·Reported By 2 ·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.