Upgrading? Which metadata should be deployed
If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
This article contains instructions for which metadata plans to deploy when upgrading RIO Education. For information on what metadata these plans contain, please see this article.
Once you have upgraded a prior version of RIO Education to a newer version, certain metadata packages must be deployed in order to complete the upgrade. These packages can all be found in the RIO Education Installer under the RIO Education - Upgrades product.
The metadata packages are grouped under different plans. Each plan is named after a version number, and contains all the metadata packages needed to deploy when upgrading to that version from the previous version. For example, the plan "RIO Education - Upgrade to v3.6" contains all the metadata needed to deploy when upgrading from RIO Education 3.5 to RIO Education 3.6.
If you are upgrading more than one version at a time, you should deploy all plans starting from the plan after the version you are upgrading from, and finishing with the plan for the version you are upgrading to.
For example, if your current version is v3.5, and you wish to upgrade to v3.10, you must deploy the following plans, in this order:
- RIO Education - Upgrade to v3.6
- RIO Education - Upgrade to v3.7
- RIO Education - Upgrade to v3.8
- RIO Education - Upgrade to v3.9
- RIO Education - Upgrade to v3.10
Community Security Setup packages
Please note that some plans contain metadata packages for the Community Security Setup. Which packages you deploy will depend on how your Community is set up.
If your instance only has a single Community that will be used by both Faculty and Student members, please select only the "Combined Community Security Setup" metadata packages.
If your instance uses two different communities for Faculty and Student members respectively, please select only the "Student Community Security Setup" and "Faculty Community Security Setup" metadata packages.
Make sure that this choice is consistent across all plans you deploy.