Manual Upgrade from Versions 8.00–9.00 to Version 10.00
With Continia Document Capture 10.00 and Continia Expense Management 10.00, Continia Software is releasing a combined upgrade guide that our partners can use to upgrade directly from Document Capture 8.00-9.00 and/or Expense Management 8.00-9.00 to Document Capture 10.00 and/or Expense Management 10.00.
Important
Note that Document Capture 2022 R2 (10.00) is only available if you're using Business Central April 2019 (v14, FOB-based) or newer versions. This means that clients using older NAV/BC versions will not be able to upgrade to DC10.00. Instead, they must upgrade to DC8.00, as this version will continue to be supported with service packs.
If you are using Document Capture or Expense Management in Microsoft Business Central online, the main upgrade will be performed automatically when you install DC10.00/EM10.00.
Migration from FOB-based version of NAV/BC to on-premises extension and/or online: See Upgrading NAV/Business Central with Document Capture Installed and Migrating Document Capture from Business Central On-Premises to Cloud.
This upgrade guide can be used with the following versions of Document Capture and Expense Management:
Document Capture
- Document Capture 8.00 with any service pack
- Document Capture 9.00 with any service pack
Expense Management
- Expense Management 8.00 with any service pack
- Expense Management 9.00 with any service pack
If the system is running an older version, you must first upgrade to the required versions.
In this version, we have upgraded the Document Capture Client Components and Server Components, and you must update these components before you start working with Document Capture and Expense Management. This guide will instruct you on how to do this correctly. The Document Capture and Expense Management objects in this version are not backward-compatible with older components, and the components in this version are not backward-compatible with older objects.
If Document Capture and Expense Management are not already installed, you should not use any information in this document.
Task 1: Check minimum version requirements
Please be sure that the current system is running one of the supported versions of Document Capture or Expense Management listed in the summary section. If not, it is very important that you follow the upgrade guide from an earlier version to DC4.50 and or EM2.60. Previous upgrade guides can be found here.
Task 2: Import updated BC license file
The upgrade process must be performed using a partner developer license.
After the upgrade please ensure to use a new/updated customer license file from Microsoft.
You must restart the Business Central Server to use the new license.
Task 3: Merge objects
If you have modified your customer's system, then check if any of the modified objects conflict with Document Capture or Expense Management objects and merge if necessary. You should merge objects in a test system so they are ready to be imported later in the upgrade process.
Task 4: Check pre-upgrade package
There is no Pre-Upgrade step in version 10.00.
Task 5: Upgrade server components
You must perform all installations described below from the Setup executable, located in the root of the product folder (Setup.exe).
Note
The installer will update the add-ins folder (Client and/or Server) in the standard installation path. Therefore, if your installation path differs from the standard Microsoft path, make sure to copy the new add-in folder to the folder your installation resides in.
To upgrade your server components, follow the guide below:
Version | Guide |
---|---|
BC14 | Only perform the following steps if you are using Business Central April 2019 (BC14):
|
Task 6: Update BC objects and data
Important
Before doing object modifications or starting the data upgrade, make sure to back up the database.
Import the new DC10.00/EM10.00 objects from the product folder. Use “Replace All” in Import Worksheet. Please note, some objects may show a warning during import as some parts of the new Version List have changed format. Set Synchronize Schema to “Later