Import an Unlocked/Managed Package
In this article, we would be discussing about how to import a packages (unlocked/managed) into the ARM application. For more information related to packages, refer to the article: Create an Unlocked/Managed Package
Step 1: Importing a Package
Hover your mouse over the Salesforce DX module and select the option: Packages
Click Import Package.
Select your version control Repository and Branch.
This list down all the packages and package versions (if any) available in your branch.
Select the packages to import.
To view the dependent packages for the selected packages, click on View Dependency Packages.
To validate the selected package with your devhub, select the devhub from the drop down list and click on Validate Package button. The green tick beside Validate Package denotes the packages and devhub are rightly matched.
Click Save. A confirmation window appears with the details of the package.
Click IMPORT. The Import Packages Log window appears.
Click CLOSE, and you'll be redirected to the Packages homepage where you can find your package recently imported.
Important Note
You can import multiple packages with the same name as long as they are from different repositories or different branches.
Step 2: Create a Package Version
What is a Package Version?
A package is a container for Salesforce metadata. It represents a distinct deployable unit of functionality that is iterated over time. You can add metadata to a package and take a snapshot of it, anytime. This snapshot is called a package version. You can create package versions any number of times. Each package version, once created, is immutable and is associated with a single package. You can install a package version in any Salesforce environment - scratch orgs, sandbox orgs, or production orgs. Installing a package version deploys the metadata that was specified when the package version was created.
Click on the + icon under the Actions tab to create a version for your package.
Next, fill in the below details:
Version Name: Version name gets auto-generated based on the package name. However, you can edit the name and enter your desired name. It is really up to you.
Version Number: Version numbers are formatted as "major.minor.patch.build". For ex- 1.2.1.8.
Installation Key: Enter the installation key that protects your package from being installed by unauthorized individuals.
Tag: Enter the tag that is required to release the package. For ex- Release 1.0.0
Version Description: Brief description of your package version.
Click Create.
Verify the log status in the Package Log screen.
Last updated
