We have a great tool in AX 2012 for upgrading EDT relations to the new structure of Table relations.
Unfortunately it does not handle system data types like UserId very well. You have to change the \Classes\SysEDTMigration to prepare the tool for all types:
One of the most often used tool is the AOT node Compare utility, which has some improvements from the past but can be changed further.
Now in AX 2012 the compare tool can be executed as CIL code rather than in the X++ runtime tier, which should give you considerable performance boost for larger code comparison. Here is a great post (The compare tool–and running X++ code as IL) from mfp about improvements that Microsoft did.
On the other hand you can do some improvements yourself by adding the following line to the SysCompare class, selectionChanged method:
Hi Friends!
Since Microsoft Dynamics AX 2012 is now booming, it is time to share some interesting features, problems and solutions for this exciting new product which is already out in the wild on the DAXRunBase blog.
In future posts I am planning to cover ways of using the Team Foundation Server and build automation, show tricks that can make everyday development a bliss, introduce using PowerShell and AxUtil during your everyday life and a lot more.
I really hope you will find the following posts useful, and a thumbsup in comments always helps to keep me motivated =)
Cheers
Vilmos Kintera
When I was playing around with images and resources in AX, I have found that Menu nodes have an AOT property called NormalImage. On this property you can provide a file name which was imported into AX under the Resource node, so your module would have this image shown in the Main menu.
But when you want to use the resource in a report, the kernel does not associate your custom image with a resource ID, and you also do not have a property similar to the menus.
The only solution that you have is to add a Bitmap control to your report, then read out the data that is being stored under the node and return the container as a Bitmap value. Here is the code:
If you are trying to look up a label under the menu Tools/Development tools/Label/Label editor, the search string matches your label string with a wildcard.
For search strings like “item” it might display many hits, and takes a lot of time to get the results. But if you enter the label on an object property and you do the lookup there, an exact match search is executed.
If you take a look on \AOTClassesSysLabel::searchStringBuildExactStr(LabelType _searchString) you can find the solution there as a macro.
If you use the same search term, then you will get an exact match:
“<item>”