Salesforce Known Issues
Trailblazer Community

Performance Edition Orgs showing as "Base Edition" in LMA

LMO , Partner

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

In Review ·Reported By 11 ·Updated 2022-04-26

LMA Workflow updates not reflecting in subscriber orgs, inconsistent statuses

AppExchange , Packaging , LMO

There is an issue at this time where workflow updates to LMO license records may not reflect in subscriber orgs.

In Review ·Reported By 9 ·Updated 2022-04-26

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 6 ·Updated 2022-02-15

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 1 ·Updated 2022-02-15

Different search results in Subscriber org tab for many orgs in LMA.

AppExchange , Packaging , LMO

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 1 ·Updated 2022-02-15

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 2022-02-10

Parsing a formula referencing to a custom field could fail with an InvalidFieldReferenceException if a custom field with the same name is in an instal

LMO

On a subscriber org which does not have a namespace prefix, if a custom field is created on a custom object contained in a managed package and there is a custom field with the same name in the custom object, and if the custom field is referenced in a formula in a lookup filter's criteria of a custom...

Fixed - Spring '17 ·Reported By 11 ·Updated 2022-02-10

LMA: Direct Login from License Object to Subscriber Console fails for subscriber org

AppExchange , LMO

LMA: Direct Login from License details page fails for Subscriber that has more than 1 package installed that is associated with the LMO

Fixed - Spring '18 Patch 13.0 ·Reported By 7 ·Updated 2022-02-10

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 2022-02-10

Fields end up in an invalid state when signed up from trialforce. Push upgrades will fail.

Packaging , Custom Objects , LMO , Partner

FieldDefinition relationships to Standard Fields on custom objects are stored in the database in the form: "<CustomObjectId>.<FieldApiName>" e.g. 01Ixx0000005ahE.Name. These fields are not remapped by the signup engine, since the field isn't totally and exclusively an ID. There's logic to partially remap...

Fixed - Spring '19 Patch 14.0 ·Reported By 3 ·Updated 2022-02-10

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.