DynamicsSubs

I hope you all are doing great and might have gone through my earlier blog on Azure APIm introduction: https://www.blogger.com/blog/post/edit/2520883737187850604/4308148657431504181 This documentation focuses through live examples as to how such a system could be effectively designed and made to work with D365. Situation: problem statement We have a 3 rd party logistics system who creates Purchase orders in DAX, validates and creates GRN in AX and subsequently posts them. Solution design a.        A batch job that creates an Azure storage file in a shared Azure folder. b.        Custom Ax services pick up the file and creates Purchase orders in D365 c.        The third party receives the purchase order in their own system and tries to replicate the same in Ax. For that I.                      It needs to call an Ax defined class that validates various information for a given purchase order. II.                    In order to do this you can define an action/method in a

  What is TAAS Table as a service is a very convenient way of high frequency, high volume data exchange, operations, without the need of worrying about the supporting architecture, speed and efficiency. I can make my data be stored and arranged as per any need, without sticking to a fixed metadata, beforehand – as compared to conventional DBMS definition. Your Table exists as an API, whereby you can call the API and enforcing PUT, POST and delete actions thereby.   Table as a service as a storage Azure table storage exists as a patterned NoSql data in Azure, resulting in a schema-less design. Table storage generally comprises of following components: Accounts: a subscription account that connects all the storage offerings(Blobs/files, queues, containers, tables) Tables: a table can comprise of several entities Entities: an entity is like a row that comprises of several properties Properties: Key-value pair Look at the following example, that comes from a TAAS on