Process Data Changes on Device

The entire synchronization concept is designed to ensure that all data transmitted from the mobile app to Dynamics is first stored in a designated table known as the Receiving Tasks. This table guarantees that all incoming records are processed in strict chronological order, ensuring no data is skipped or lost during the process.

This method also provides resilience against poor internet connectivity. Even in cases of unstable or interrupted connections, the system ensures that incomplete or delayed data transfers are accounted for. Data is only processed once all records have been fully and successfully received by Microsoft Dynamics 365 Business Central.

All data received from the mobile device is processed in exactly the same order it was entered into the device. Whether it involves newly created records, modified data, or deletions, every change is transmitted and applied to the corresponding Dynamics tables using Web Services during synchronization. This guarantees consistency, integrity, and accurate reflection of the mobile user’s actions within the central ERP system.

Moreover, the Receiving Tasks table serves as a detailed log per device, providing complete traceability that confirms every data package has been received reliably. This logging mechanism ensures full transparency and accountability within the synchronization process. It is crucial that users regularly monitor this table to verify that no issues have occurred during the data processing phase. Any problems that arise at this stage are not related to transmission failures, but rather to processing difficulties within Business Central, which are handled in a second step, after receipt.

Therefore, the synchronization process is clearly divided: first comes the reception of data, then the processing. If issues appear in the Receiving Tasks table during processing, it is essential to review how data ownership and responsibilities are defined within the business process on the mobile app. The Anvaigo Mobile App should be designed in such a way that these ownership rules are clearly established and respected. These are not technical issues, but rather questions of process design and correct configuration. Ensuring these definitions are properly set up is critical for reliable and consistent synchronization.

Data Changes by User

All changes done by the user on cards or lists run the following commands in Dynamics: VALIDATE, INSERT(true), MODIFY(true) and DELETE(true). This way your code in your tables will be executed as well.

Due to processing data using Dynamics Web Services,  some features are not available and might require some changes in your table triggers. Find more information here.

Data Changes by Anvaigo Script

If you use Anvaigo Script for adding, changing or deleting data, you can decide if you want to run Dynamics table triggers during a synchronization process. The use of SETVALUE versus VALIDATE decides if you want to run the OnValidate-trigger, MODIFY(false) versus MODIFY(true) decides if you want to run the table trigger OnModify. Same for OnInsert and OnDelete. Furthermore, these parameters define whether you want to run your local Anvaigo Mobile App Triggers.

[[ Do not run VALIDATE trigger. Equals Rec.Name := 'new Name'; ]]
Rec:SETVALUE('Name', 'new Name');

[[ Run VALIDATE trigger. Equals Rec.VALIDATE('Name', 'new Name'); ]]
Rec:VALIDATE('Name', 'new Name');

[[ Do not run OnModify trigger. Equals Rec.MODIFY(false); ]]
Rec:MODIFY(false);

[[ Run OnModify trigger. Equals Rec.MODIFY(true); ]]
Rec:MODIFY(true);