By Henning Lund - August 04, 2020
Anyone who has tried to make a data integration with Microsoft Dynamics 365 for Finance and Operations has met the obstacle, that the system does not support timestamp. That makes it troublesome to identify new and modified data. There are several ways to solve this.
The problem is that if you don't want to transfer an entire table every time you want data synchronized, then you need a way to detect, which data is modified or added.
So how do you deal with it in the best way?
The first method requires that a developer creates a timestamp field on each table, or creates a similar functionality that gets updated every time a record i modified. But there are several issues with this method.
Another method is to create comparison tables in AX where the developer can compare new and old values and by this detect which records that are modified. This is in many way a more solid way to detect changes, however it also comes with some challenges:
The mirror is a highly optimized variant of the above Method 2. The mirror is a separate binary SQL database (MS SQL, MySQL or similar) designed to solve the timestamp issue without having the constraints in the above methods:
If you want to discuss the integration with Microsoft Dynamics 365 for Finance and Operations or any timestamp challenges you may have we are always happy to help.