Upgrade to the Latest Version of Digitise Apps
The Digitise Apps software is generally supplied as a download from our web site. Therefore, before you can upgrade to the latest version of Digitise Apps, you will need to download the latest version from the web site. You, or someone in your organisation, should have received an email, when the Software Licence was purchased or renewed, providing full details of how to download and unzip the software and giving details of your Software Licence.
The Product Download can be used to perform a new install of Digitise Apps or to upgrade an existing version of Digitise Apps or its predecessor, MX. We recommend taking a backup of your existing installation before performing an upgrade.
This topic relates to upgrading, for information about installing Digitise Apps on a clean machine see Perform a New Install.
-
Whilst all new versions of our software are given extensive testing, every live environment is potentially different. It is therefore important that you test any existing Solutions with a new version in a test environment BEFORE you upgrade your live systems.
When upgrading from a previous version of MX, please note the following:
-
If you have an existing app created with a version of MX prior to MX v10, there have been changes to the way Foreign Keys are treated within Data Sources. If you want to update your app to take advantage of the improved treatment of Foreign Keys, you will need to load your Project into the latest App Studio, right-click on the Data Source name in the Data Sources Pane and choose Update Schema. Click on OK. The Schema diagram should be displayed. Remove any existing Foreign Key data items and then add them back in.
-
In versions of App Studio earlier than MX v10, when creating an ADO Database Data Source or viewing the schema of an existing Data Source, only the user-selected tables from the database would be queried for their contents. From MX v10, however, because of support for Foreign Keys, all tables in the database have to be queried in order to fully establish Foreign Key relationships. This may result in a longer delay whilst the schema is retrieved. A dialog box is displayed indicating progress during the process and includes a Cancel button.
-
In MX v10 the ADO Database Data Source Property Protect Unsynched Records was removed.
This Property affected uploading data from the mobile device to the back office. Existing apps created using a version of MX prior to v10, will retain their current setting if edited in the latest App Studio but you will not be able to view or edit the setting.
-
Versions of MX prior to MX – 2020 Vision Edition allowed you to include Google's Fabric Crash and Usage Data Reporting within your MX apps. Google have now replaced this with a new version called Firebase Crashlytics and so Digitise Apps no longer supports Fabric Crashlytics and has moved over to Firebase Crashlytics instead.
When upgrading, existing Standalone Apps and pre-configured Clients which had the old Fabric Crashlytics enabled will ignore the setting and no Crashlytics data will be sent. If you want to enable the new Crashlytics within these apps or Clients, you will need to rebuild the app or Client within the latest App Studio and enable the new Firebase Crashlytics.
The following topics give more information about upgrading different components:
Upgrade MX to Digitise Apps (App Server and development PCs)
Upgrade an Existing Version of Digitise Apps (App Server and development PCs)