I took some run-up and showed a couple of things within the last blog posts I want to bring together now for a small example how you can build an small but useful extension to the new Microsoft Dynamics AX. Amongst others, there were examples for event subscriptions, project export/import, how to use the Browser class, create an extension package and a way to search the Wiki cleverly. Today I want to combine all of that into a simple solution that uses extending techniques only and adds the ability to search the Wiki via Bing directly from AX.
Today I want to show how you can export and import projects. It’s very easy and similar to what can be done in AX 2012.
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.
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.
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.
After migrating an solution to the new Microsoft Dynamics AX (AX7) it’s likely that at some point you’ll face the fact that the Code Upgrade Service removed formerly existing DeleteActions from tables. Why does it do this and where are the artifacts now?