function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
AquacdrAquacdr 

Issues with LMA

I'm trying to do the following and am almost there but not yet...

 

Scenario:  We will be creating a managed package and will eventually list it publicly on the appexchange so in our first development iteration I'm trying to prove out the licensing that goes around this with using LMA.  

 

So far I have done the following:

 

1.  In a DE org I created a LMO

2.  Created a managed package and uploaded it into appexchange (private still)

3.  Created a listing and set the default license values

4.  Created a demo DE org and then used the link for the package that was given during the upload process

 

Results:

 

1.  Looking in the package object in the LMO the record was created

2.  The package version was created and linked to the package

3.  The license object contained no license record

4.  Of course then no lead was generated.

 

I have changed nothing to the default installation of the LMO and am wondering if the problem is can you track licenses with lma on a private managed package?  Does anybody know? 

 

AquacdrAquacdr

I figured it out...it was a OE (operator error).   I was using the install link for a package version that wasn't linked to the LMO yet...

 

It works great.