How-to update the Anveo Mobile App?
Different types of updates
Anveo Mobile consists of several components: The Anveo Mobile App Client on the mobile devices, the Anveo Mobile App Builder in Microsoft Dynamics, and the Anveo Mobile App Configuration as data in the Anveo Mobile App Builder such as Sales App, Service App and Delivery App. It may also be desirable to update the Microsoft Dynamics version.
Update of the Anveo Mobile App Client
If the Anveo Mobile App Client is installed in the usual way (without mobile device management, MDM), an update is performed automatically if automatic updates have been activated in the mobile device. If automatic updates are turned off, please open your store on the device and update manually. If an MDM solution is in use, an update can be delivered in a controlled manner. The operation of an MDM solution is up to the user and usually causes further administration effort and costs, but offers a controlled update of this component.
Update of the Anveo Mobile App Builder
For this, we recommend booking the update package. In this case, the Anveo Mobile App Builder is updated to the latest version while the Dynamics version remains unchanged. This means that new functions of the app setup tool are available, but the app setup itself is not supplemented or changed.
If you or your Microsoft Dynamics Partner would like to run the update by yourself, you will find a “Update Process & Changelog” file in the release folder with further instructions.
If you want to hand-over the update to Anveo: The service description of the “Anveo Mobile App Update Package” is available here.
Please note: An active Anveo Service Plan is required to update to the latest Anveo version.
Update the Anveo Mobile App Configuration
The Anveo Mobile App can either be completely replaced or manually updated with new features included in newer versions of the Anveo Mobile Apps such as Sales, Service or Delivery. An automatic update is not recommended and not possible. It must be checked in the dialog which functional scope is to be transferred to the already implemented app solution.
Please note: If you replace the current Anveo Mobile App Configuration of the Sales App, Service App or Delivery App with a new one, the existing customizations must be implemented manually.
Microsoft Dynamics version update
When the Dynamics version is updated, the Anveo Mobile App Builder is usually updated first and then the old app setup is transferred to the new system.
Here we recommend the following procedure:
- Installation of the new Microsoft Dynamics system
- Installing the Anveo Mobile App Builder in the new Dynamics system
Important: The new Dynamics system requires new Anveo objects. Please request them from Anveo Support. - Export the old app configuration from the old system and import it into the new system.
- Updating the configuration: e.g. setting up the new delta service replication, if applicable.
- Analysis of the changed or missing data structures in the Anveo Synchronization Package setup. Missing tables and fields are indicated by numbers without names. These must either be added as new tables/fields in the new system, or the app setup must be adapted.
- Verification of the function through test runs by the developers.
- Customization of the app until verification by developer successful.
- Test runs of the key users according to the Best Practice Guide.
- Customization of the app until testing of key users successful.
Please note: Migrating from the classic C/AL FOB-objects to the new Extension development using AL code requires more time. The core structure of Anveo is compatible, so an export and import of the configuration is possible. However, there are more customizations required.
A Microsoft Dynamics update technically results in a new installation of Anveo. This also automatically updates to the latest Anveo version. As a result, you will be able to take advantage of the latest version. Please note that an active Anveo Service Plan is required. In addition, depending on the version differences, changes in the configuration are required.
We recommend booking the Anveo Quick Start package for active support of the project.
Please note: As the Anveo Mobile App offers different types of installations, for example with and without Universal Code Initative support (type AB versus type C3), with or without AzureSQL support, a change of the type of installation is like a “Microsoft Dynamics version update”. Please have a look at the different types on the “System Requirements” manual page.
Typical scenarios are:
Moving from an OnPremises-installation to Business Central Online
Moving from a Classic SQL-Server to AzureSQL
Moving from Non-Universal-Code to the variant with Universal Code Initiative-Support
Moving from FOBs (C/AL) to Extensions (AL)