Search Results

As of the Spring 14 release of Salesforce (API 30), ISV's can delete some metadata components included in a Managed - Released package: Custom Buttons or Links Custom Fields Custom Objects Custom T …

It is possible by going to the following relative URL when logged in to your License Management Organization (LMO), passing in the desired target Subscriber Org Id: /partnerbt/lmo/subOrgLogin.apexp?d …

This doesn't look like an issue coming from Skuid, it appears that you still have a custom trigger named "SpringCMOpportunity" in your org which is running some logic which is looking for some functio …

This is possible by querying on the UserPackageLicense object, available as of Summer 14, as described in my answer to this post: Get the list of users licensed for a managed package private static …

Sometimes ISV's provide global methods in a Utility class that allow for Protected Custom Settings, particularly Checkbox fields such as your "Triggers Disabled" field, to be toggled by clients. I'd c …

From the "Subscribers" / "Subscriber Support" tab included with the License Management Application (for ISVforce and OEM partners), Partners can see an overview of a given customer/Subscriber's org, i …

If I have a Managed Package with Namespace ns2, with package components that depend on / extend components in ns1, then ns1 must first be installed in an org before ns2 can be installed - as ns2 has b …

I think there's really 3 approaches: COMMON 3RD PACKAGE: Include a common interface as part of a 3rd package that both Package A and B depend on. This way you can consistently dynamically instantiat …

If you want users to install your package from AppExchange into their existing Salesforce org, you will need to have some warning / info message in your App's description to let them know that the NPS …

See the answer to this question: Assigning Managed Package Licenses in a Sandbox By default, when you refresh a Sandbox of a Production org that has a Managed Package installed with per-user license …

Whenever you deploy managed package code, your tests will always be executed against the target org you are deploying into. If you are installing your managed package into another org, then your test …

As you've quoted from the docs, NO, you can't "upgrade" to a Partner Developer Edition (PDE) / Super-Sized dev org, nor can you migrate your namespace to a different org. However, you can request add …

In order for your Batch Apex to work from the InstallScript context, both your Install Script and the Batch Apex class will have to be marked without sharing, or at least you will need to remove the w …

Even though the managed VF page runs on a different domain, e.g. namespace.na12.visual.force.com, prepending <namespace>__ to your page names will automatically send the user to this domain, no matter …

Has anyone out there in the ISV/OEM ecosystem ever signed up customers in one LMA org, with official License records being created, and then, say, decided to spin-off this application into a separate …