My company wants some data in AX 2009 to be synchronously integrated with AX 365. Example every time a record in InventTable is created/modified in AX 2009 a trigger will create/modify this record in AX 365.
Think twice if you really need synchronous integration; it may have significant negative impact on both ERP systems. Also, synchronous integration requires that both systems are running. What if D365FO is down, because a new version is being deployed? What would happen with the information that an item was modified in AX 2009? You might want to consider a reliable messaging system, for instance.
D365FO offers services for synchronous integration, most importantly OData services. But you’ll need some queueing mechanism anyway, if you don’t want to lose any updates. If you don’t use a middle-tier service handling it for you (e.g. Service Bus), you’ll have to implement it inside AX 2009.
Hi Martin,
Sorry it is an asynchronous integration. How can we expose data in AX 2009? We can do an AIF but the outbound result will be an xml file. For AX 365 we can do data entities and webhooks will do the middle-tier service handling. Do you have any suggestions?
Thanks,
Ruel
There are many ways and which one is the best for you depends on your specific requirements.
In AX 2009, one option is indeed using AIF file system adapter to generate XML file, which you can later transform to some other format. Or you can write some custom code, e.g. serializing the data to JSON and exporting it to a file or putting a message to a queue.
In D365FO, data entities are surely the right way, but you can use them in several ways. For example, you can import files with the help of Recurring Integrations Scheduler, you can use Logic Apps or you can call OData services or the packages API from your own application.