back to resources
UNMANAGED PACKAGES
July 14 2022 • 10 min read

BUSINESS CHALLENGE

featured image

All the orgs that are affiliated with a production org can be called as related orgs. Using change sets metadata components can only be moved between related orgs by establishing deployment connections.

What if we want to move components between unrelated orgs?

Unmanaged packages can be used to move metadata components between unrelated orgs.

WHAT IS AN UNMANAGED PACKAGE?

Unmanaged packages are typically used to distribute open-source projects or application templates to provide developers with the basic building blocks for an application

They can be used to move metadata or components between two different related/unrelated orgs.

After Installation, Users can modify the components based on their requirement.

up 1

HOW TO CREATE AN UNMANAGED PACKAGE

  1. Click the Gear Icon → Click Setup.

    up 2

  2. In the Quick Find search and Select Package Manager.

    up 3

  3. Click New.

  4. Enter Test Package as Package Name, choose the required language.  Add a user for Notify on Apex error which is optional. User will receive an email once the package is uploaded, click Save.

    up 4

  5. Once you click the save button. You will be redirected to another page (Please refer to the image below). Click on Add to add the components. 

    up 5

  6. You can choose the component type and add the required components.

  7. On Selecting the custom object from the component type. You will see all the custom objects in your org → Select the custom object which you want to add to the package.

    up 6

  8. Click on Add to Package.

    up 7

  9. It will automatically add all the dependent components like Lightning Record Pages, Custom Fields, List Views, Page Layouts etc.

    up 8

  10. Each component type should be added individually.

  11. If you want to add a flow, click the Add button again and choose Flow definition as the component Type → Select the required flow which you want to add to the package → Click on Add to Package.

  12. Automatically dependent components( if the flow sends any email ) like Classic Email Templates, Email Template Folder, Email Alert will be  added After adding a flow to the package.

    up 9

  13. If you want more information about components that can be added to Unmanaged packages please refer to the link .

  14. After Adding all the components, click Upload button

    up 10

  15. Enter Version Name and Version Number as per your requirement.

    up 11

  16. If you have “Release Notes” or if you Wish to provide “Post Install Instructions” then select the URL option and Specify the link to the respective resources. Optionally you can set a password to protect the package.

    up 12

  17. Click Upload again.

    up 13

  18. After the upload is done, you will see the Installation Url. (Refer to the below image)

  19. Copy and save the URL.

HOW TO INSTALL UNMANAGED PACKAGE

  1. Open a New Tab in your browser and Paste the link that you have copied previously.

    up 15

  2. If you are going to install it in a sandbox make sure to replace the domain with https://test.salesforce.com or you can also replace it with the target orgs domain.

    up 16

  3. If you are already logged in to your target org, you don’t need to enter user credentials. If you are not logged in, you should enter the credentials like user Id and Password for the target org.

  4. It will open the package installation window as shown below.

    up 17

  5. Choose the install options according to your requirement, Here we are installing it for all users.

  6. Click Install.

  7. Click Done after the installation completes.

    up 18

  8. You can verify the installed package and its components by heading to Installed packages from Setup.

    up 19

  9. Click on the Package Name and click View Components.

    up 20

  10. You will see the components of the package.

    up 21

LIMITATIONS

  1. The package creator does not have control over the components of the package.
  2. Unmanaged packages are not upgradeable.
  3. You cannot add Salesforce Classic and Lightning email templates from Private and Public email template’s folders to a Package. These templates do not appear in the list. We recommend you to create a separate folder for templates that you want to add to the Package.
  4. Templates built with the email template builder that contain references to attachment files cannot be packaged and do not appear in the list.
  5. You cannot upload Lightning Email Templates to Unmanaged Packages.
  6. Not able to add Approval processes in managed or unmanaged packages.

Wrapping it up

In this Blog we have covered how to create and install unmanaged Packages.

Leave a Comment

Your email address will not be published

© 2022 Digital Biz Tech