There is a good explanation about how you can create a new model in a new package in the Wiki already. I want to talk about this a little anyway because I think I can add some useful information concerning package references and especially source control.
After a short break I’m back (I was on vacation all March and try to reintegrate myself to daily life since then 😉 ) – first of all with a small post concerning the Wiki. It is tremendously helpful but there are teething troubles with the integrated search functionality.
In this post I’ll shortly tell you about the batch service in development (and other one-box-) environments and what you need to do to debug it.
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.
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.
For AX 2012 there’s a tool called CAT (Customization Analysis Tool) in LCS that gives you a detailed report for one or more models you upload to it. With the new Microsoft Dynamics AX this was moved to the development environment (the virtual machine you use for development) and is a command line tool now. It seems to be referred to as CAR (Customization Analysis Report) more often.