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.
With the new Dynamics AX there are new APIs that are needed because of the technological changes. If you want to navigate the user’s browser to a different URL programmatically (and not by providing a link they can click) this can be done very easily by using the new class Browser.
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.
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.
In case anyone missed it I wanted to quickly echo an overview on the great series of blog posts mfp created about the new and changed features of X++. All of them are must reads for any developer who wants to work with the new Microsoft Dynamics AX.