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.
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.
While Technical Conference is underway Microsoft made the first version of the new Microsoft Dynamics AX available. You call it RTW, which is short for Release To Web (the old-fashioned term would have been RTM – Release To Manufacturing – which meant that the CDs can be cut). And yes, I was wrong about the date somehow but still the release party (besides the conference that is held in Seattle right now) is at the date I named.
Although I’m not at the conference I was able to take a first look at RTW (carrying version no 7.0.1265.3015, platform 7.0.4030.16079) and would like to point out what got my attention at first sight.
You might have heard that AIF (Application Integration Framework) is no longer supported in the new Microsoft Dynamics AX. Though the SOAP-based custom services still are there and work as they did in AX 2012. And the services are provided JSON-based, too. Pretty much everything you need to know at the start is available in a great wiki article, the Microsoft Dynamics AX Services Technical Concepts Guide.
The one thing I’d really like to point out is that there are lots of good examples provided by Microsoft and made available on GitHub. You can use them to learn how things work and as a suitable starting point for your implementations. The root address of the examples is Microsoft / Dynamics-AX-Integration.
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.