Known Issues · Partner
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 5 ·Updated 4 days ago
Some customers may not be able to upgrade managed package in their partial copy sandbox if the package contains asset file component. Error on the component: 1. An unexpected error occurred. Please include this ErrorId if you contact support: ... (2100495319) AssetFileName: An unexpected error occurred....
In Review ·Reported By 1 ·Updated 5 days ago
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
When a managed object standard button is overridden by lightning component for "Lightning Experience Override" by developer in the packaging org, and the package is installed in a subscriber org, the override for "Lightning Experience Override" cannot be updated by package versions remove the lightning...
In Review ·Reported By 32 ·Updated 12 days ago
When custom metadata records are deleted by a developer in the packaging org, the records is incorrectly marked as deleted in the version when it was added to the package, causing various issues.
In Review ·Reported By 4 ·Updated 25 days ago
When creating an org from AMER region via environment hub, user receives "verify your account" email from firstname.lastname@example.org, instead of email@example.com.
In Review ·Reported By 6 ·Updated 26 days ago
Some customers may experience this issue after clicking "link namespace" in their dev hub org: a blank window is opened instead of a window prompting to login to dev org.
In Review ·Reported By 17 ·Updated 2019-04-18
- Apex class can refer to a managed package object's (managed) custom fields in them. - The managed package can choose to delete the field in their next version and add few more new fields. - Upon upgrade of managed package, even though the field is deleted inside the managed package, the field...
No Fix ·Reported By 1 ·Updated 2019-04-16
Users may notice an error message "Not in package.xml" when attempting to validate or deploy an inbound Change Set. --- When a Developer deletes a component from their package, the component continues to exist in the subscriber org even after the package is upgraded. When the component is...
In Review ·Reported By 10 ·Updated 2019-04-13
When a trial org is created from a template, pie chart wedges is null and an error is displayed on the dashboard: Error: One or more of the fields selected in the component is no longer available in the report. Use the dashboard component editor to select one of the available fields. Same error...
No Fix ·Reported By 9 ·Updated 2019-04-04
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.