If you are upgrading an existing SmartConnect installation, and the current SmartConnect version is a version prior to SmartConnect 10.0.0.51, SmartConnect must be upgraded to version 10.0.0.51 before proceeding with a SmartConnect 2010 or later installation.
When upgrading SmartConnect the following steps should be followed:
| • | Ensure that the current version of SmartConnect is at least 20.12.2.40. If you are using something earlier, a two step upgrade will be required. |
| • | Back up all your Microsoft Dynamics GP, CRM, or NAV databases. |
| • | Back up your SmartConnect database. |
| • | Remove the current version of SmartConnect using the add/remove programs option. |
| • | If the SmartConnect or Salesforce web service was installed, ensure that the website(s) have been removed from IIS |
| • | If the SmartConnect windows service has been running, ensure that the service has been stopped. |
| • | Open the SmartConnect client and run the System Maintenance process (should be triggered automatically) |
For installations using the Microsoft Dynamics GP Connector:
| • | Complete the steps under Upgrading SmartConnect. |
For upgrades from 10.0.0.51:
| • | Run the system maintenance on your 10.0.0051 version of SmartConnect (Tools – SmartConnect – System Maintenance). You need to do it in each company because the maps are company specific in each database. |
| • | Follow the update instructions starting at section 3.1.2.3 Upgrading SmartConnect on page 27 of the SmartConnect 2012 manual.Complete the steps under Upgrading SmartConnect, then the steps for installations using the Microsoft Dynamics GP Connector. |
| • | After getting SmartConnect update to 2012, then go ahead and update to SmartConnect 2018. |
Upgrading scheduled maps
| • | Scheduling has changed in SmartConnect 2010 SP1 and instead of scheduling maps via the windows scheduler a windows service is installed that manages the scheduling and running of maps. Because of this change, maps that were scheduled in SmartConnect 10.0.0.51 or SmartConnect 2010 must be re-scheduled manually using the scheduling interface. |