Please read the following information carefully if you are about to upgrade your Microsoft Dynamics with Resco to a newer generation.
Back up your app projects
We recommend that you back up all your app projects before upgrading Dynamics.
-
Select App Projects from the Administration menu.
-
Select any project and click Export.
Additional content to back up:
-
Note down/take screenshots of project priorities and roles assigned to projects; this information in not included in the exported projects.
-
Back up your reports.
-
Back up your questionnaire templates.
General principles
To ensure that the Resco app works seamlessly, the metadata of the source and destination systems have to be the same (at least for the part used in the Resco app). Tables and columns used by the app also have to be the same. Usually, upgrades are done by exporting data and metadata (solutions), and if all solutions match in the source and destination systems, all should go well.
-
Read the following chapters for guidelines, even if the source and destination versions don't match your exact case.
-
If possible, perform a dry run by upgrading a clone of the original system or a similar developer environment.
-
As always, schedule adequate time for end-user testing to mitigate unexpected issues.
If you are a partner in charge of an upgrade, don't hesitate to create a request for consultation on the Resco support portal.
Upgrade to Microsoft Dynamics CRM 2015 & 2016
If you opt for an automatic update of Microsoft Dynamics CRM 2013 Online, all Resco tables (tables that start with “resco_”) should stay unharmed. There are no other steps you would need to perform. After a successful update, you should be able to run the Resco Suite and App Configurator the same way as you were used to and all of your app projects should be intact.
If you are migrating from Dynamics CRM 2011/2013 to 2015 or 2016, verify that App Configurator is migrated as well. If not, you have to import/download Resco Suite again after the upgrade (so that Resco tables are recreated on the server). If you changed any security policies, organization-level Localization, Plugins, or Maintenance, you must perform all changes again.
Make sure to download the Resco Suite/App Configurator version corresponding with the new version of your CRM server.
Import your app projects afterward.
Note
If you are upgrading from the Woodford 7.4 and older, you must import/download Resco Suite even if Resco tables were migrated correctly during the upgrade. This is because Dynamics CRM 2015 and 2016 require the presence of a newer solution version that the previous versions of the Woodford did not have.
Migrate to Microsoft Dynamics CRM 2013
Migrating to Dynamics CRM 2013 should go smoothly and automatically when it comes to Resco Mobile CRM. After a successful upgrade, you should be able to run the App Configurator the same way as you were used to and all of your app projects should be intact. This means there are no special steps you would need to perform.
Note
If you are upgrading from Woodford 7.4 and older, you must import/download Resco Suite even if Resco tables were migrated correctly during the upgrade. This is because Dynamics CRM requires the presence of a newer solution version that the previous versions of Woodford did not have.
App projects not working
If app projects are not working, please follow these few simple steps:
Verify that Resco Suite and App Configurator are still available in your organization. Go to Solutions in your CRM organization’s Settings section and check its version number.
If you cannot see any App Configurator solution in your organization, you need to import it into Dynamics.
If you changed any security policies, organization-level Localization, Plugins, or Maintenance, you must perform all changes again.
Second, start the App Configurator. If you can see your app projects, you are ready to use them again. If not, you need to import and publish them again.
Note
The standalone version of Woodford is discontinued. Start the App Configurator directly from Dynamics as a web application.
Migrating from own premises to cloud
If you are migrating an on-premises Dynamics installation into the cloud, you can make the migration seamless for your mobile users by setting up a particular security policy. Limitations apply.
Tenant migration
If you are migrating your environment to a different tenant:
-
Back up your app projects.
-
Have Power Platform support to initiate the migration. (Microsoft documentation)
-
Verify that App Configurator and all app projects remain available after the migration. If not, reinstall App Configurator and/or import the necessary app projects.
When in doubt, contact Resco support.