During development and especially debugging the new Microsoft Dynamics AX you are to face the question which table Id or field Id actually stands for which table. In AX 2012 you saw the Ids in the property sheet of selected AOT elements; those were stored in the model database. With AX7 this has changed.
As I reported before (Release Date for the New Microsoft Dynamics AX!) the new AX gets released March 8 / 9, 2016, accompanied by a Virtual Launch Event that is held twice to enable people from all the different time zones to attend.
Some time ago I wrote about the ways to perform a database synchronization from Visual Studio in the new Microsoft Dynamics AX. Clearly this relates to development environments. Here’s one way to do a synchronization without VS – you’ll need it when you have a deployed environment.
The release date for the eagerly awaited new version of Microsoft Dynamics AX (also known as AX7) is:
March 8 / 9, 2016
Source: The Virtual Launch Event(s) were announced to partners for those dates.
In AX 2012 there’s a macro you can extend to suppress best practice checks (SysBPCheckIgnore). There are a lot of issues related to it, e. g. its size and compilation, the fact that it belongs to exactly one model per layer (colliding with other solutions) etc. Of course there are some workarounds but clearly there was room for improvement. Here’s what we have now and how you deal with it.