13

Just run the following command: sfdx force:package:installed:list -u <alias|username> This will give you all of the packages installed, including the 04t "AllPackageVersion" Id that you need to install an app. Sample output: === Installed Package Versions [4] ID PACKAGE ID PACKAGE NAME NAMESPACE ...


7

I have never tried this before. But using dynamic objects you can do this. Here are idea to get you started. Store the package details and object, field in some custom setting or custom label. Now make a dynamic SOQL to query package details. If you found the details then create dynamic instance of sObject and create new record of it. As you are not direct ...


6

Such error messages represent internal platform failures (or gacks as they are sometimes known) rather than anything in your Apex code, this is why your Apex Exception User is not receiving anything. The underlying reason could be a range of things, a bug in the platform code or an error relating to a feature or incompatability in the org your trying to ...


6

Change the install URL to their instance instead of login or test, and paste it into your address bar after logging in.


5

Here is one (of many) test methods for an install handler in our code: @IsTest static void testAdls() { // Clear to make sure the value is set by the install handler Options__c cs = Options__c.getInstance(); cs.ActivitiesOfDailyLiving__c = null; upsert cs; Test.testInstall(new ClaimsInstallHandler(), new Version(8, 5)); // Custom ...


5

No, this isn't possible. You can set an InstallHandler to create data, deploy a metadata file, etc. Generally, though, any other actions you will want to take should be either (a) documented in a post-installation doc, or (b) set up as a Visualforce page that the administrator should visit after installation. You may want to submit this as an idea on the ...


4

FallenPhantasm, Good morning. I'm the author of ngForce. As it turns out there's a grunt task for installing it in your org. Once you've cloned the repo and run npm install just run: grunt deploy It will prompt you for username / password / security token. It will then build the latest version of ngforce, and upload it along with it's apex components to ...


4

Once you get the unmanaged package link ,you will replace login with test Lets say your unmanaged package link is https://login.salesforce.com/packaging/installPackage.apexp?p0=04t28000000B4ng Your package link for sandbox is as below https://test.salesforce.com/packaging/installPackage.apexp?p0=04t28000000B4ng Edit Also note it takes significant ...


4

The subscriber org cannot update the callback and Canvas URL once packaged . In this case its preferred to have administration instructions for the org administrator to create the connected app while you can package other code .Also you can always read the canvas app name from the custom setting .


3

Salesforce is a little finicky when it comes to removing stuff. Unfortunately (and I've lived through this before), removing pages and controllers is a two step process. First, you have to make sure that all the dependencies for a given class are removed (or the dependency removed). Only then, in a second update, you can get rid of the class. So, do this: ...


3

Was the package just created? I get this error if I attempt to install a package immediately after its created. Waiting 5 minutes or so resolves the issue.


3

Please check that you are installing the correct package. If you are installing on a developer edition org, use this package. If you are installing in production or sandbox, use this one. I just tried it again on another fresh developer org and it worked so the package does not have any issues. If you still have issues, it may have to do something to your ...


3

The Salesforce Metadata API is the only API that will do this for you. You can use the listMetadata operation to accomplish this, here is a previous question with answer detailing this, How to get a list of the managed packages (including version numbers) installed in an org?. If your interested in doing this from Apex, you can find a library that exposes ...


3

It seems to be namespace issue: Try replacing to below syntax: <span id="gaconnector_pages_visited_list"><apex:outputField value="{!lead.Pages_visited__c}" /> </span>


3

You can get away with the problem of namespace in your lightning components by crafting your own wrapper class structure for your data attributes. The blog post here describes how to create message or wrapper class https://medium.com/@mohitkumarsrivastav/transitioning-from-a-visualforce-developer-to-a-lightning-developer-c23c269157bf#.jviqi965l So in ...


3

Not doable via sOQL. Using JSForce, you can do a Metadata Retrieve requesting the following members conn.metadata.retrieve({ apiVersion: '39.0', singlePackage: true, unpackaged: { types: [{ 'members': ['*'], 'name': 'InstalledPackage' }] } }) The response would return all installed packages and and an ...


3

You missed configuration steps prior installation From installation guide: Before installing the AppExchange package, the Set Audit Fields upon Record Creation org permission is required. When we migrate attachments and files, we set system field values like Created Date, Created By, Last Modified Date, and Last Modified By. These fields are considered ...


3

Spark Edition is likely a version of Personal Edition or Free Edition, rebranded to fit the Lightning theme (a Spark is smaller bit of electricity than Lightning). These orgs were extremely limited in nature, allowing minimal customization and minimal CRM features (really, just Accounts and Contacts). These types of orgs were common circa 2009, but were ...


3

There is a tooling object for same for that named "packageinstallrequest" . You can query status field to know the install request status https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/tooling_api_objects_packageinstallrequest.htm Update Further research revealed that this tooling object tracks install and upgrade only ...


3

No. Each managed package is tied to a specific developer org. It cannot be migrated to another developer edition org. If you've lost access to that developer edition, you will have no way to upgrade the package, and you would need to create and install a new package. It would have a different namespace, though, so you could install them side-by-side, copy ...


2

As Bob said, have you tried: {!URLFOR("/apex/namespace__MYVFPAGENAME?"+ IF(Account.Id!=NULL, "aid="+ Account.Id+"&", "") + IF(Contact.Id!=NULL, "cid="+ Contact.Id+"&", "") )} This of course will mean that your button no longer works in your package dev. org(s) as the namespace is not present there. I'm not sure there's an elegant solution for ...


2

One of possible way to get around this error is by enabling the Chatter in target org (where you are installing the manage package). You can enable chatter settings via Setup-->Customize-->Chatter-->Settings ( Enable "Turn on Chatter and Global Search features") Once this is done then you will see the settings on Cases -> Support Settings page as well as ...


2

Make sure you have specified the class name which you want to run on Post install of the package into the Post Script Install field in the package detail page(In the packaging org). This field is a lookup of apex classes and you can add this by clicking on the edit of package detail page. You can specify your class as public or global but you must not ...


2

If it is the Twilio Helper Library for Salesforce that you ave installed, then it looks like you need to use the TwilioRestClient.getAccount().getSmsMessages().getPageData API to get the SMS messages. It looks like you will have to poll i.e. make the call periodically and you can get Apex code run in that fashion by using the Apex scheduler. It is up to you ...


2

If you turn on chatter before you install the package the issue should be resolved. The setting is in Customize | Chatter | Settings.


2

Log a case with SFDC support, you'll get a response similar to: You should now be able to install the affected package. There was a delay in our package replicator process that has now caught up. Upon installation of this package, please let me know if you require further assistance with this matter. As you can see, there's not much anyone outside of ...


2

Are you sure you need to add the namespace prefix for your custom fields? As it looks like - you are giving them the namespace prefix but not to the object. From what I understand - if you are within the context of the package - you do not need to add the namespace prefix, can you try it without, or try to add the prefix to your object name? Also - adding ...


2

While it's not quite the same as having an installable package, you can achieve the identical end effect of an upgradeable unmanaged package by using the Metadata API. When an Unmanaged Package installs in your org, it creates a package in the org just like if you were developing an unmanaged package (look under Setup -> Create -> Packages) and all the ...


2

An OEM package is basically the same thing as a normal managed package; OEM vs. ISV is about who's providing licensing. With the OEM licensing model, you create contracts with salesforce.com for the licenses, and your clients create contracts with you. With the ISV model, users already have a salesforce.com contract, and form a separate licensing agreement ...


2

To avoid this error is necessary to have communities enable first Setup -> Communities -> All Communities


Only top voted, non community-wiki answers of a minimum length are eligible