What is Unmanaged package ?
- In simple words, we are packing all the required components(assume this set satisfies one requirement/functionality) as one file and uploading it to cloud(Back to platform/AppExchange). Once we upload to cloud, Salesforce will generate an URL for us, by using this URL, anyone can install this package. In the destination org, all these package components are editable.
Note : If your package contains any Triggers/apex classes then it is mandatory to maintain 75% code coverage otherwise unmanaged package will not upload.
I already know deployment using ANT/Workbench/Changeset then again what is the use of using unmanaged package ?
- If we add one component then implicitly all the dependent components will be added to the unmanaged package.
-In the destination org, if we uninstall the unmanaged package then all the components related to that unmanaged package will also get deleted. In simple words,we will have control over installed packages and it is easy to track the components based on functionality.
How to create Unmanaged package and how many we can create in one org ?
- We can create unlimited number of unmanaged packages in one org.
- To create unmanaged package => Click on "Setup" -> type "Packages" in Quick find
-Click New Button
-Click "Save" button and add the required components. Finally click on "Upload" button(once, you are done with adding the components).
After clicking "Upload" button, we will get the below screen
Once we fill all the details in the above screen, then in the next screen, it will generate an installation URL.
Now, we are all set to use this URL. To use this URL, we need to login to another salesforce org and paste that installation URL in "URL bar".
Click "install" button. It takes few minutes to install. You can find the installed package details from the below path : Setup => Type "Installed packages" and the screen looks like below :
Hurray..!! are we done... ? no boss still 2 more questions are left .. ;)
What is the meaning of Unmanaged packages are not upgradable ?
-After installing the package in destination org, if we go back to source org and add some more components to the same package and if we upload then it will generate a new Installation URL for new version. With the new version URL, if we come back to destination org and try to install, then it will throw an error.
The solution is : Uninstall the existing version in the destination org and install the new version.
Can we delete Unmanaged packages in Source org ?
- Yes we can delete only if it is deprecated. If you want to delete an unmanaged package then in package it self you will see "Deprecate" button click on that then you can able to delete. There will be no effect to already uploaded unmanaged packages in destination orgs but the installation URL will not work if we try to install in new orgs. We can also "undeprecate" the unmanaged package if required.
Report to check supported components to add into Unmanaged package. CLICK HERE
tHiNk gooD and dO thE bEsT.........MANJU NATH 🌝
- In simple words, we are packing all the required components(assume this set satisfies one requirement/functionality) as one file and uploading it to cloud(Back to platform/AppExchange). Once we upload to cloud, Salesforce will generate an URL for us, by using this URL, anyone can install this package. In the destination org, all these package components are editable.
Note : If your package contains any Triggers/apex classes then it is mandatory to maintain 75% code coverage otherwise unmanaged package will not upload.
I already know deployment using ANT/Workbench/Changeset then again what is the use of using unmanaged package ?
- If we add one component then implicitly all the dependent components will be added to the unmanaged package.
-In the destination org, if we uninstall the unmanaged package then all the components related to that unmanaged package will also get deleted. In simple words,we will have control over installed packages and it is easy to track the components based on functionality.
How to create Unmanaged package and how many we can create in one org ?
- We can create unlimited number of unmanaged packages in one org.
- To create unmanaged package => Click on "Setup" -> type "Packages" in Quick find
-Click New Button
-Click "Save" button and add the required components. Finally click on "Upload" button(once, you are done with adding the components).
After clicking "Upload" button, we will get the below screen
Once we fill all the details in the above screen, then in the next screen, it will generate an installation URL.
Now, we are all set to use this URL. To use this URL, we need to login to another salesforce org and paste that installation URL in "URL bar".
Click "install" button. It takes few minutes to install. You can find the installed package details from the below path : Setup => Type "Installed packages" and the screen looks like below :
Hurray..!! are we done... ? no boss still 2 more questions are left .. ;)
What is the meaning of Unmanaged packages are not upgradable ?
-After installing the package in destination org, if we go back to source org and add some more components to the same package and if we upload then it will generate a new Installation URL for new version. With the new version URL, if we come back to destination org and try to install, then it will throw an error.
The solution is : Uninstall the existing version in the destination org and install the new version.
Can we delete Unmanaged packages in Source org ?
- Yes we can delete only if it is deprecated. If you want to delete an unmanaged package then in package it self you will see "Deprecate" button click on that then you can able to delete. There will be no effect to already uploaded unmanaged packages in destination orgs but the installation URL will not work if we try to install in new orgs. We can also "undeprecate" the unmanaged package if required.
Report to check supported components to add into Unmanaged package. CLICK HERE
tHiNk gooD and dO thE bEsT.........MANJU NATH 🌝
Comments
Post a Comment