ISVforce Guide
jNewer Version Available
License Management App FAQ
- How do I change my License Management Organization?
- Contact Salesforce support. License records in the current LMO don't move to the new LMO. They stay with the original LMO.
- Why aren't Lead and License records being created in my LMO?
-
- Your LMO hasn't been associated with your package.
- Your package version hasn't been registered.
- There are mandatory custom fields in lead, license, package, and package version custom objects.
- The LMO Lead Manager (the lead records owner) is not a valid active user.
- The before_ triggers are preventing lead creation.
- For more possibilities, see Troubleshooting.
- Why can't I see the Modify License button?
- Customize the page layout by adding the Modify License button to your page.
- A customer installed my package before I associated it with my LMO. How can I manage the license record?
- Ask the customer to install your package again without uninstalling it.
- What happens when I decrease the number of licenses below the current number of licensed users?
- All users still have access until a system administrator in the installer's organization revokes the extra licenses.
- Why should I install the LMA into my production Salesforce organization?
- The LMA is an important part of a partner's sales, billing, and marketing of a package on the Salesforce Platform. Installing it in a separate organization means they can't manage package licenses as a part of their sales and marketing process.
- Installing the LMA into the customer's production organization means they can manage the lead, trial, licensing, and billing as part of their overall Salesforce dataset.
- Can I automate the assignment of package licenses to users in the subscriber organization?
- Yes, you can use the API to assign or revoke licenses for managed packages installed in your organization. For more information, see the PackageLicense and UserPackageLicense objects in the SOAP API Developer's Guide.