İsmail Ozcan

thank you  Pete Ward In a previous post I walked through how to make changes to your online web catalog directly from Dynamics AX 2012 ( http://blogs.msdn.com/b/dynamics-coe/archive/2013/02/04/updating-your-commerce-catalog-directly-from-dynamics-ax.aspx ).  This powerful feature showcases the truly integrated, omni-channel retail solution that is Dynamics AX. In this post, I'm going to look at what's happening in the background and walk through the data flow of this process. So to begin, let's have a look at a very simple picture representation of some of the components involved in this process.  (and yes there are a number of elements involved that I've left off but this will get us started).   So let's step through what's happening when we publish our catalog to the web. Step 1: Publishing the catalog from Dynamics AX to the Commerce Run Time database When you publish the catalog in Dynamics AX and run the A-1075_OC job, the CRT Synch Service...

Building on  this post on listing elements in a model  and  this post on putting a list in a HTML file  I wanted to quickly just show an easy and quick way to create list elements in a model to HTML. The PowerShell command is easy, and the results are swift and usable. For this example I'm going to list the contents of a hotfix. (axmodel -model 'Hotfix-KB2909140-Foundation' -details).elements | select name, elementtype, path | ` sort path | ConvertTo-Html -CssUri http://skaue.com/ps.css | Out-File c:\KB2909140.html The HTML-file can be viewed using your favorite browser.

AX utilizes SQL Indexes in order to speed up queries to the database. It is important that any index created is analyzed for its usage pattern; for example, will the query only be made once per day, or thousands of times in a loop? It might not be worth it to create an index for a query which is only executed once per day. The reason for this is that anytime an INSERT, UPDATE or DELETE statement is executed, any affected indexes must also be updated. A side effect from a lot of INSERT, UDPATE or DELETE statements is that over time that index can become fragmented. Fragmentation occurs when SQL can no longer fit data into the free space allocated for an index, or space is removed within the middle of a page of data. It handles this by creating another page for the index to store its data in. Excessive fragmentation can lead to poor performance if a lot of records are being selected as the data is not kept contiguous. This can lead to increased IO and CPU. One workload that is particu...