|Available in: Salesforce Classic|
|Available in: Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions|
|To upload packages:||“Upload AppExchange Packages”|
|To install and uninstall packages:||“Download AppExchange Packages”|
Salesforce supports upgrades for managed packages only. Publishers can publish an upgrade for a managed package and notify installers that the new version is available. Installers of a managed package can then install the upgrade as follows:
- Before you install an upgrade, determine if the app you installed was from a managed package. Look for the
Managed - Installed icon on the detail pages for each component and on the list of packages installed.
If the app you installed is not from a managed package, upgrades for it are not available.
- Then, install the upgrade in the same way you would install any other package from the AppExchange. If the publisher provided a link to the new version, follow the link to the package posting and install it in your organization. The first page of the install wizard lists the current version you have installed, the version you’re about to install, and a list of additional components included in the new version.
Notes on Upgrading Managed Packages
Consider the following when upgrading a managed package:
- All existing custom objects that were previously deployed will still be deployed. Salesforce prompts you to deploy any new custom objects or previously undeployed custom objects.
- Profile settings for components in a package are editable by the customer but not upgradeable by the package developer. If the developer makes changes to any profile settings after releasing the package, those changes won’t be included in an upgrade. Customers will need to manually update the profile settings after upgrading the package. In contrast, permission sets in a package are upgradeable by the developer, so any changes the developer makes will be reflected in the customer organization after upgrading the package.
- If the developer chooses to add universally required custom fields, the fields will have default values.
- Translation Workbench values for components that are “editable but not upgradeable” are excluded from upgrades.
- If an installed package has Restricted
API access, upgrades will be successful only if the upgraded version does not contain any s-controls. If s-controls are present in the upgraded version, you must change the currently installed package to Unrestricted
- When you upgrade a package, changes to the API access are ignored even if the developer specified them. This ensures that the administrator installing the upgrade has full control. Installers should carefully examine the changes in package access in each upgrade during installation and note all acceptable changes. Then, because those changes are ignored, the administrator should manually apply any acceptable changes after installing an upgrade.