20

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.


6

It was not really clear from the announcement or from most of the documentation, but Salesforce Data Mask is actually a paid feature, and if you want to use it you need to talk to your Account Execute to purchase licenses. As per the documentation on installing Salesforce Data Mask: Ensure that your organization has the Data Mask User permission set ...


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 ...


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 ...


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

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 ...


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

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 .


4

Use the -w parameter so that each command waits for confirmation, and things proceed in order: sfdx force:org:create -w 10 -s -f ./config/project-scratch-def.json -a ScratchOrg sfdx force:package:install -w 10 --package 04t0M000001mF9bQAE sfdx force:package:install -w 10 --package 04tG0000000LKgXIAW sfdx force:package:install -w 10 --package ...


4

The relevant documentation reference is the ISVforce Guide, under Editing Components and Attributes After Installation. It covers most metadata types and explains the manageability rules that will be applied after you ship a component in a managed-released package. As a general rule, any attribute called out as "Developer Editable" can be changed ...


4

Just for the record, consensus is an Apex static variable that the InstallHandler implementation sets and other code tests i.e.: /** * Referenced by triggers. */ public inherited sharing class Triggers { /** * Want to special case logic related to install handlers: the InstallHandler * implementation can set this and other code e.g. ...


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

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

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

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

The Salesforce CLI (sfdx) makes it very easy to get a list of installed packages and their version ids: sfdx force:package:installed:list Output: { "status": 0, "result": [ { "Id": "0A33A000000QgeWSAS", "SubscriberPackageId": "0331C00000083VFQAY", "...


3

Contrary to some answers, you can use SOQL to retrieve this information. You just can't use it in Apex. In the developer console, if you check the "Use Tooling API" option, the following query will return the information you want: SELECT Id, SubscriberPackageId, SubscriberPackage.NamespacePrefix, SubscriberPackage.Name, SubscriberPackageVersion....


3

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


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

You can create a class which implements InstallHandler interface and write your logic in onInstall method this method will be invoked after package installation. global class PostInstallClass implements InstallHandler { global void onInstall(InstallContext context) { //Your logic to add permission sets. } } For more information you can ...


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 ...


3

So far you can't. The only thing you can run is Apex Classes compilation with the --apexcompile flag. However, starting Winter 21, code coverage should be enforced for Unlocked Packages installation. The original post from PM Dileep Burki is available here, feel free to go there and give your thoughts about it. Enforcement of Code Coverage in Unlocked ...


3

SFDX conveniently has a feature that does this. sfdx force:package:installed:list -u org-name-or-alias You can directly use the package Ids from the list to install the packages into other orgs. Note that you'll need the "password" if that version is password-protected, which may be a whole separate problem, but this will at least get you most of ...


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