Known Issues · LMO
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...
Release In Progress - Spring '19 Patch 14.0 ·Reported By 3 ·Updated 3 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
Organization detail page accessed from Subscriber tab does not displays correct percentage value for API Requests, Last 24 Hours. Used Data Space and Used File Space display correct percentage value.
Fixed - Spring '19 ·Reported By 1 ·Updated 2019-02-09
Performance Edition Orgs showing as "Base Edition" in LMA.
In Review ·Reported By 3 ·Updated 2019-01-14
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 2018-03-23
There are instances when a time out occurs when trying to search for an org via the subscriber support feature. Typically these orgs reside on a sandbox org and are very large in terms of storage. R&D has found that there is a process in the LMA that is not correctly finding the orgs in the subscriber...
Fixed - Spring '18 Patch 7.0 ·Reported By 1 ·Updated 2018-02-10
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.
In Review ·Reported By 4 ·Updated 2017-12-04
Partners are getting "Insufficient Privileges" error when accessing some tabs from the installed package, logged in to the subscriber org via License Management Organization (LMO).
No Fix ·Reported By 1 ·Updated 2017-11-29
There is an issue at this time where workflow updates to LMO license records may not reflect in subscriber orgs.
In Review ·Reported By 5 ·Updated 2017-10-10
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 1 ·Updated 2017-04-11
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.