InventDimDevelop macro

InventDimDevelop macro is used to mark places in the application where specific inventory dimension(s) are referred from the code explicitly. The idea behind it is to help developers to find all the places that potentially have to be updated if a new inventory dimension is added.

For example, the following code should be marked with InventDimDevelop since size, color and configuration are referred explicitly:

#InventDimDevelop

this.ConfigId = inventDimCombination.ConfigId;
this.InventSizeId = inventDimCombination.InventSizeId;
this.InventColorId = inventDimCombination.InventColorId;

However, the following code processes all dimensions in a loop, so newly added dimension will be handled automatically. No need for InventDimDevelop.

container dimFields = InventDim::dimFieldList();
int h, y;
;

for (h = 1; h <= conlen(dimFields); h++)
{
    y = conpeek(dimFields, h);
    this.(y) = _inventDim.(y);
}

Exporting and importing compiler output

I am probably not the only person who had faced the following problem – if you are doing some major change, like renaming of a table or a class you are compiling the AOT to get all the places where references to renamed object should be changed. The problem is that the resulting error log can be easily lost, for example, by pressing reset or closing AX by accident. Unfortunately in this case it cannot be restored easily, only with yet another AOT compilation. To avoid recompilation I found out for myself great functionality that allows to export and import compiler error logs. It is accessible from the Compiler output window->Import/Export.
It is also interesting fact that AX uses html format to store error logs.

Wizard wizard

There is a tool in AX that allows automatically generate code for new AX wizards. This tool is accessible from the Main menu\Tools\Development tools\Wizards\Wizard Wizard. By using this tool a new project with a wizard form, controlling class and a menu item will be generated. There will be also several methods created on the controlling class and on the form. Actually, the code generated by the tool is a good start for implementing a new wizard.

MenuItem types

What is the difference between MenuItem types - Display, Action and Output, except that they reside under different AOT nodes and that different intrinsic functions should be used to access them via reflection?

I know one - they are displayed with different images in the navigation pane:

Are there any other differences?