Downgrade to a Pre-10.1 Version of MX

Changes in MX v10.1 to the way MX stored passwords both on the MX App Server and on mobile devices necessitated changes to the structures of the configuration databases in which passwords are stored. This means that the configuration databases are not backwardly compatible with those used in versions of MX earlier than v10.1. As a result, if, having upgraded to the newer Digitise Apps, for any reason you want to revert to a pre-v10.1 version of MX you will need to delete or edit the relevant databases before you can re-install your earlier version. Note that on mobile devices you cannot edit the local databases and will need to uninstall Digitise Apps on the device which will delete any associated local databases at the same time.

The Digitise Apps App Server is compatible with earlier versions of the MX Client, including Standalone Apps built with earlier versions of the Client. Consequently, if you were to downgrade a Client or a Standalone App you should only need to downgrade the App Server software as well if you are downgrading because of an issue which affects both the server and the client. Likewise, the latest Digitise Apps Client is backwardly compatible with earlier versions of the MX App Server software and so downgrading the App Server software would not necessarily require you to downgrade your Clients and Standalone Apps as well.

In addition, because Standalone Apps are self-contained, you can run Standalone Apps built with different versions of the MX and/or Digitise Apps Client on the same device at the same time. This means that if you were to experience a problem with one Standalone App but other Standalone Apps on the same device didn’t have that problem, you may only need to downgrade the Standalone App which was experiencing the issue.

On most Platforms you can run both a standard Client and Standalone Apps on the same device. In this situation, once again, if you were to experience an issue you may only need to downgrade those individual items which experienced the problem.

The sub sections which follow provide additional information: