lost in ax

Hi, regarding the synchronization of retail transaction from stores to HO, I received some inquiries what are the alternatives when there is an issue in the store that will prohibit Async Client from sending data to HO – for example, network issues, hardware failures. Well, there is always the ever helpful DMF entities . It is limited – however, the 3 main tables needed to successfully Calculate Statements every end of day are all provided as standard entities. If you are using the demo data from Contoso, chances are you will not be able to see these entities. However, go to Data import export framework à Setup à Target entities , just click New and drop down to Entity field and select as what has been provided above. This should automatically populate the columns Staging table , Entity Class and Target . Note : If you have a legacy POS with transactions which you want to integrate with AX, you can just use this and just make sure that it will follow th

Hi, In my previous post, I have discussed about the details of downloading data from Head Office to Retail Store. Today, let’s discuss the process of synchronizing transactions from Retail Stores to Head Office. In a hindsight, the Async Client service in store is responsible in creating the RPF files and saving it in the Upload File Path Working folder . The RPF files of the retail transactions are created every interval as specified in the Async Client Configuration . Running the P-Job is unnecessary to create the RPF files, what we need is a secure connection between Async Client and Async Server every upload interval. Basically, the P-Job is for importing the transactions from the Upload Working Folder to Dynamics AX. So how does the Async Client know which record to include in every creation of RPF files? In AX 2012 R3, the Channel Database is maintaining the table called crt.TABLEREPLICATIONLOG . This table contains the following field: FIEL