9

The use case is that we have added additional licensing parameters to the LMA License object that our managed package reads from the LMA via a @RestResource site added to the LMA org.

This works fine for production orgs that have an LMA License object but not for sandboxes that do not have a corresponding LMA License object. Hence the quick fix would be to identify the production org id (when in the sandbox org) and always pass that in the read request...

PS The lack of a license for sandboxes is awkward in other situations too - see LMA should create licenses for sandbox installs.

Improve this question
2
  • I don't know of any way of doing this, but maybe you could somehow capture the production org Id (post install script or at some point when they run your app in product) in a private custom setting, then read it once your in the sandbox?
    – Andrew Fawcett
    Nov 11, 2013 at 12:34
  • 1
    I just posted an idea for Salesforce to add a Lookup to the corresponding Production Org's license record: LMA Licenses for Sandboxes need Lookup field to the Production Org License
    – zachelrath
    Oct 28, 2014 at 15:44

1 Answer 1

Reset to default
4

I don't know of any way of doing this, but maybe you could somehow capture the production org Id (post install script or at some point when they run your app in product) in a private custom setting, then read it once your in the sandbox.

Improve this answer
2
  • Thanks. This license logic is already in the post install script and has a private custom setting so I'll go with that unless something simpler gets posted here. I'll mark your answer as accepted once its all working.
    – Keith C
    Nov 11, 2013 at 13:07
  • Welcome, neat LMA integration btw! ;-)
    – Andrew Fawcett
    Nov 11, 2013 at 14:02

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .