Salesforce Known Issues
Trailblazer Community

Org Edition is incorrectly displayed in LMA Org's 'Subscribers' tab.

AppExchange , Packaging , LMO

The Org Edition is incorrectly displayed in LMA Org's 'Subscribers' tab. A developer or professional edition org that installs the customers package will show as an Enterprise Edition org in the partners LMA.

In Review ·Reported By 4 ·Updated 3 days ago

AppExchange Checkout Customers Receiving Unexpected License Change Emails

AppExchange , LMO , Partner

Prerequisites: - You sell your solution using AppExchange Checkout. - You use Checkout Management App (CMA). - In CMA, the "License Changes" Checkout notification is enabled. AppExchange Checkout customers may have received email notifications about changes to their app licenses when they did not...

Fixed ·Reported By 0 ·Updated 11 days ago

License record for Sandbox refreshed Org or Trialforce Org are not showing in LMA

LMO , Partner

License record for Sandbox refreshed Org or Trialforce Org are not showing in LMA

Fixed - Winter '21 Patch 16.2 ·Reported By 130 ·Updated 22 days ago

Performance Edition Orgs showing as "Base Edition" in LMA

LMO , Partner

Performance Edition Orgs showing as "Base Edition" in LMA.

In Review ·Reported By 10 ·Updated 23 days ago

AppExchange Checkout Management App creating error message rather than purchase confirmation

AppExchange , LMO

For partners using the Checkout Management App (CMA), some are seeing an error message delivered by email when customers install the package.

Fixed in version CMA 1.14 ·Reported By 5 ·Updated 2021-06-22

Newly released package versions not appearing in LMO unless it is installed when LMO and packaging org are on different instance

LMO , Partner

Newly released package versions not appearing in LMO unless it is installed when LMO and packaging org are on different instance.

Fixed - Spring '21 ·Reported By 6 ·Updated 2021-02-16

Logging in to Subscriber Orgs as a non-admin user from Licenses page fails

LMO

Non-system admin users cannot log in to Subscriber Orgs, even if they have the permission: "Log in to Subscriber Org".

No Fix ·Reported By 6 ·Updated 2021-02-01

Internal server error when managing protected custom setting in a subscriber if a field is deleted by developer

LMO , Partner

Partners may get internal server error when they login to a subscriber org via LMA, and then manage a protected custom setting, if a field was deleted in the custom setting by the developer.

No Fix ·Reported By 4 ·Updated 2021-01-28

After a package installed org moved to other instance License record still shows old instance on LMA

LMO

The partners can see instances of package installed org on License Management App(LMA). When package installed org moved to other instance by Org Migration, license record still shows old instance on LMA. Refreshing license does not fix the issue.

In Review ·Reported By 0 ·Updated 2020-11-16

Winter'21 - In LMA, Lead records are not created when customers install packages

LMO

After Winter '21 Patch 9.0, license records are created on LMO but Lead records are not created when customer install the package. The issue occurs when duplicate rule for Lead object is deactivated.

Fixed - Winter '21 Patch 10.7 ·Reported By 19 ·Updated 2020-11-15

1 to 10 of 23 | Next

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.