Monitor your instance for accidental changes

You know when you have a test instance, and out of the blue users report something is not working as before. One of the probable reasons for this (of course, there are many more) is someone made a change on another model / layer that is not getting noticed, and may overshadow good code or create a different behavior.

AX Project Explorer - AX 2012 - IEIDE Tools

I managed after a couple's months work (not that it took so long to develop), to put together one of my oldest ideas for enhancing the AX IDE: Project Explorer. You can download it from here: http://ieide.codeplex.com.

Merge Tools (II) - AX 2012 - Create a project from t-sql output

 Once you run the script to get the conflicting objects: http://axfaq.blogspot.ro/2014/02/merge-tool-ax-2012-another-useful.html, you can save them to .csv (the objects list), and then use the .xpo below to create a project with these objects:

Merge Tool - AX 2012 - Another useful script to get info

 Say you have a dilemma about the objects you get in a new model that you are going to apply on your instance, wondering if you will have conflicts (overshadowed code with the existing one); I am not going to talk about the standard ways of determining this; what I use instead is a t-sql script that gives me the objects nodes' that are in both models (this is taking into account the AX granularity of storing/handling the objects when):

Import VS Projects - AX 2012 - Critical error Invalid AOT path specified

I'm sure that if you tried to move Visual Studio project without the help of model file (aka importing from xpos) you are getting errors, most likely: Critical error. Invalid AOT path specified. and Serious error during import of Visual Studio Project and ImportError at Token: (null) LineNo: 0.