≡ Menu

During project build process following operations are performing. All these operations are one by one after each other.

  1. Metadata and X++ code validation.
  2. Best practice checks.
  3. Report RDL Generation
  4. Compilation and creating .Net assembly.
  5. Label and resource file generation.
  6. Database Synchronization.



Following are some recommendation.

  • Using Camel casing.  Variable name must be in camel Case for example table buffer for CustTable must be similar custTable.
  • Avoid keyword. Avoid system keywords.
  • Company name of  Prefix with company name or project,  For example if my company name with Al then all custom table, Custom form, Extended data Type, enum must be start with al suppose.  AlFileInstallmentSchedule, AlCustTable. table.
  • Maintaining consistency, throughout the customization prefix used are consistence, so elements are easily locate.

Recently I completed a customization.  Basic requirement is workflow type have to decide on Certain enum based value at run time.

For dumpy example, I have two customized type for Sales Order. External Sales and Internal Sales.

And Workflow based on same query or table will be different for external sales and internal sales.

For this you have to left empty Workflow in Design Property of form.


You have to over write. LoadWorkflowConfiguration


For more reference Kindly explore the ledgerjournaltable form.


Recently I upgrade the Dynamics Ax 2012 R3 RTM environment to CU12.

You can find official Microsoft guide for CU12 form following link.


Following are my notes during upgrade process.

First step to download patch KB3199741.


This link requires  login to partner source. You have to add email address and then Microsoft send you email where you can download patch.


Second step is to download cu12 silpstream.  For this you have to login LCS .


If you don’t have any cloud environment No issue Microsoft still let you download Cu12 slipstream.

create a new project if there is no project available in LCS.

I create a project with Name test.

Click on it and let the project open and navigate the screen and then click on Update.

From next screen download Cumulative Update 12 sliptream

Download depends on speed of internet. Size of file is round 931 MB.


I copied both patch and slipsteam on required folder and extract both in one folder. First I extract the patch and then extract the slipsteam.




Now I run the AxUpdate



Accept and Continue.




But I face the problem that Visual Studio 2013 Dev Tools are not enable. For it solution I found following link which help me.


In short, I stop the Installation. And do the following steps.

Run the Dynamics Ax 2012 setup and Uninstall the Visual studio 2012 tools.

Install Visual studio 2013 VS2013_U4 on machine.

Download and install Report Viewer 2012 runtime component. You can found it from following link.



After all these step I again run the Cu12 setup and Visual 2013 tools are enabled.

Check this box and click on next.


After that I restart the AOS service. And open the AX client and select option from update check list and select first option.

Let the complete the database synchronize, Compile and Full CIL.

My environment is successfully Upgrade to CU12. Now next step is code merge or code upgrade That is not part of this post.

If you want new installation  direct to CU12. Then copy content of Dynamics Ax 2012 R3 into hard disk and then extract slipsteam to update folder. And run the Default setup. Hopes this will work.










On running report, following error message appear in info box.

The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://tempuri.org/:queryBuilderArgs. The InnerException message was ‘Element ‘http://tempuri.org/:queryBuilderArgs’ contains data from a type that maps to the name ‘http://schemas.datacontract.org/2004/07/XppClasses:SrsReportProviderQueryBuilderArgs’. The deserializer has no knowledge of any type that maps to this name. Consider using a DataContractResolver if you are using DataContractSerializer or add the type corresponding to ‘SrsReportProviderQueryBuilderArgs’ to the list of known types – for example, by using the KnownTypeAttribute attribute or by adding it to the list of known types passed to the serializer.’. Please see InnerException for more details.




  • Stop AOS service.
  • Stop Sql Server Service.
  • Start SQL server Service.
  • Restart SQL Server reporting services.




After Installation and configuration, When I connect the Entity store and establish DNS error, I got following error.





I found that Data Import and export framework did not installed on machine.




I log this error for my future reference I got its solution from Deepak Agrwal Sahib, He blog this issue on following link



I observed that Many developers are using Power BI with Dynamics Ax 2012 R3 by using Direct SQL server connection on Dynamics Ax database. Which is not good approach? This will expose Dynamics Ax 2012 database outside Dynamics Ax 2012 security. Especially when you expose or deploy Power BI on public URL.

With entity Store, Microsoft provide near to real time database access to Power BI.

In this approach, you can extract data to external database by Designing entities and data extraction from Dynamics ax tables and populate that staging entities and then to database. And this process can schedule into Dynamics Ax.


This approach is faster and more secure in the sense

  • Only required data available for Query, Unnecessary fields and table already removed.
  • No extra overhead on OLTP Dynamics Ax 2012 Database.
  • You can create more indexes on target database to faster fetch. As compare to indexes on Ax tables which creates performance overhead on Dynamics Ax.
  • Instead of Creating complex data mart, cubes and complex queries. We can create simple table structure and build dashboard on them.
  • Certainly external database can share and access on Internet or reporting is much more secure instead expose Dynamics Ax 2012 database for reporting.


For reference you can explore following links.






Microsoft release the Entity Store for Dynamics Ax 2012 R3 back in May 2016.

But somehow I decide to explore it. So today I decide to Install Entity store on my local VM. And My local vm had Dynamics Ax 2012 R3 RTM. No other Dynamics Ax 2012 Update Installed on machine. Entity stored is already part of Cu 11 for Dynamics Ax 2012 R3.


So First step is download and install KB. You can find It from following link



I have to enter my email address and Microsoft send download link for patch.

I recommend to explore the following link for Installation of any update for Dynamics.



For this article I just extract the self-extract file.


Extraction result in folder something like


This file is again extracted exe. On its extraction it creates two folders


And again these two folder contains two self-extracted exe files..

On extracting these exes, one update for Model store and second for Kernel update.

Model Store Update:

So First I decide to install update for Model store.

Before that I stopped the AOS service. Otherwise update process takes unnecessary time.


So I Click on update Ax exe in Application folder.


Click on Next


Accept and Continue



Select you model store and Click on next.


On this steps you find conflict then first resolve them. In my clean installation there will be no conflict. Press next.




Click on Install.


And finally Update is successful.



Kernel Update.

Now I decide to install what ever exe at Kernel folder.

So I go the extracted folder and run the update ax exe there




Accept and Continue



Click on Install


Finally it also installed successfully.



Post Installation update challenges:

After installation when I start AOS service and open Ax Client. I found check list, with different options for example database synchronization, compilation and full cil Generation.

In my case, this check list did not perform anything.


So closed the Ax client and in Windows command prompt, I run following command. Remember, run Windows command prompt as run as administrator.


AXUTIL set /noinstallmode

Now open Dynamics Ax client and perform following steps.

  • Synchronize the database.
  • Full compile and resolve any error.
  • Generate Full CIL.


Interestingly I got errors. And errors are related to Payroll some symmentic dll. Each line shows error 99999.

I used very strange trick. Just add new empty line and add empty comment //. Save it and compile and as result error resolved. I resolved all these error 99999 by same way.

More details I follow my own link.






After that, I found Entity store menus in Import export framework.



DNS and Entity store connection.

Now open Windows control panel, Administrator tools.



Select ODBC Driver 11 or it depends on installation.




Enter Name of User dsn.


Set default database.




Now test the connection.







Now go back to Dynamics Ax client and click on entity store. Select on User DNS. And set User DSN in last step. And click on test.










After upgrade process, Dynamics Ax checklist dialog did not let me do anything. 2016-11-24_21-51-51


So closed the Ax client and in Windows command prompt, I run following command. Remember, run Windows command prompt as run as administrator.


AXUTIL set /noinstallmode

Now open Dynamics Ax client and perform following steps.

  • Synchronize the database.
  • Full compile and resolve any error.
  • Generate Full CIL.



I took picture, not share from where, But certainly from Microsoft Slide. Yaa, SL , GP Nav also part of it.



What’s New In Dynamics Ax 2012 R3 Cu12

Microsoft release update Cu12 for dynamics Ax 2012 R3. Microsoft Also release the what’s new document to describe what in this Update. You can found it in this location

This picture is Micorosft property, I took it from PDF Shared by Microsoft

This picture is Micorosft property, I took it from PDF Shared by Microsoft