AX 2012 Generic Conceptual Modelstore Promotion Methodology

Below is a simple conceptual check list of tasks that need to be performed to promote a model store from one environment to another. Your specific implementation may differ slightly based on environment size and third party tools that you have configured.

AX 2012 Model Store Promotion Methods, part 1

     You have just written some awesome code, and of course unit tested it, and can't wait to get it into your test environment. You know you don't want to use an XPO to move your changes because this is generally a bad idea almost always. So, what can you do?

Job to Bulk Assign Organization Security

Assume you have one company already live on AX and things are well with them. Now you are bringing a second company online and adding them into the same environment as the first company. You will want to assign everyone from company 1 to only be allowed to see stuff for company 1; same with company 2. Below is a job that will bifurcate security by domain for each company.

We have Users in domain and domain. we want users to see ABC and AB1 companies stuff and users to see companies XYZ and XY1.



AX 2012 Database Log Cleanup Automation

The database log is a great tool to capture and troubleshoot odd or unexpected behaviors in AX. Depending on what and how much you log, there is a lot of helpful info that can be stored for review later. However, if you are collecting info, you either need someone to clean up data you no longer want or need or just let it sit and take up space which could slow down finding meaningful info on newer entries.

AX 2012 AIF and Batch Cleanup Automation

Logging for the AIF and Batch system is a great tool to identify what is going on and when things go wrong. Sometimes the errors could be a little more descriptive but all in all still useful. However, sometimes the tables that contain all of the logging and related info can, over time, become huge and add unnecessary work for your database server(s) and AOS(s). I wrote this batch executable class to help with mundane administrative tasks so a person doesn't have to do them. This will do the following:


AX 2012 Enum Dictionary For Reporting

I have run into several instances where I would like an easy way in SQL to convert an enum into its label equivalent. Converting some stuff by hand just to get meaningful data can be tedious; LedgerTransType is a good example. So, I created this simple solution. The attached project allows you to dump out to a table, called AAX_EnumDictionary, all of your enums so you can join then in on a report to get the labels. This is language independent and can be configured to write out only the enum labels for the system language, or all languages.

AX 2012 Starter Project

To help keep all code projects organized, I created this shared project. you simply load it into your environment. When you have a new project, duplicate this shell project, rename it and get to work. All elements have a place so you can view your work as a subset of what is in the AOT.

Understanding the AX Framework File Extensions

I found this article and this article to be very interesting. Although I rarely deal with those files, it is nice to know what each extension does at a very high level.

Learning X++

When trying to get into the world of AX, it can be daunting. There are all sorts of types, extended data types, classes, tables, queries and so on each serving a purpose. But, at an even more basic level, there is the language that powers all of those items. Learning the language at a very basic level is important to get into the more complicated stuff. check out for a list of all the kernel functions.

ADO Vs ODBC in DAX 2009

There are two very popular ways in DAX to get data from an external data into AX in some fashion. These are ADO and ODBC. The first item to note is that ADO cannot be used by a batch job because, behind the scenes, this is a COM component and those can't be used by the batch job system. So, if you want to use a batch job to grab data, you should use ODBC.  The next issue that may arise is that ODBC DSN's come in two flavors: 32 bit and 64 bit. The AX client is 32 bit but many application and DB servers are now 64 bit.

Subscribe to RSS - blogs