For one thing, AX is no more a WinForms application, it is a website. There
is no "AOS” as such, my friends. Though still a couple of Windows
services run on the server side:
·Batch management services that “Polls and
executes AX batch requests.”
·DIXF service that “Executes import/export logic
for the Microsoft Dynamics AX Data Import/Export Framework”.
Disclaimer: All screenshot are made from RTW development box. Other environments’ settings may
differ.
It is probably the toughest
topic for developers to grasp and get used to and the most cardinal change for
internal code architecture. The idea as I see it is to make the huge standard codebase modular
and loosely coupled and promote AX architects and developers to do the same
with their code.
Packages, models and dependencies
In AX 2012 and before the
whole application code existed within one namespace split by layers and models.
You could call or reference any code in your Dynamics AX instance from any
other place. We all know the upsides and downsides of this approach.
So what is new in Microsoft
Dynamics AX 7 for developers and technical consultants comparing to all
previous versions? We’re witnessing without exaggeration the most radical
change in Dynamics AX history inspired by the current technological trends and
proposals from other ERP vendors.This release is mainly technical with some
important functional changes though.
It is tough to pick out the
most important among the numerous changes. Here is my chart of innovations from
the technical point of view. I tried try condense the essence of every change
into a couple of sentences.
Web client and server.AX 7 is a website, browser is the
client. UI metadata is rendered into HTML5, CSS and JavaScript. No X++ code on
the client and no EP, of course. No ActiveX and Managed Hosts either.
.NET
integration. X++
and other metadata are stored on disk, compiled into CIL assemblies and
executed by the server’s CLR. Development is done in Visual Studio only. Some
changes to X++ syntax and model. Support of TFS / VSO integration and automated
builds.
Authorization
and Office 365 integration. AX 7
users must have Azure Active Directory account in order to access the
application and be authorized using OAuth2.
Cloud
deployment and ALM.
Production environment can only be deployed in Azure and may use SQL Azure as
DBMS. Non-production environments can be deployed in Azure or on-premise as pre-set
VMs provided by Microsoft. Pricing is subscription-based. ALM done through LCS
- a new cloud service with a lot of nice tools and methodologies.
Codebase architecture. The whole codebase, including standard
and custom code will be split into packages that are connected with one-way
dependencies. You may reference objects only within the same and dependant
packages. A new concept of extension - a non-intrusive way of customizations
together with event-driven approach form a totally new architecture,
customization and deployment ways. Package is compiled into a binary Nuget
package for deployment.
Integration,
data management and services. AIF
gets replaced by various SOAP, REST and JSON services and DIXF that is based on
Data entity - a kind of view used for integration throughout the system. More
tight two-ways integration with Office.
Task
recorder. It is
difficult to classify it to any other category. Allows to record, document and
playback all user actions from browser. A great tool for automated testing and
education.
BI. No more SSAS cubes, instead real-time
BI that leverages SQL Server Column Store Index capabilities. Close PowerBI
integration. UI-embedded user-adjustable KPIs.
SSRS
Reporting, Workflow, Security.
Cosmetic changes.
The
main deprecated features. EP,
RoleCenter, .NET connector, SSAS cubes, Virtual companies, ActiveX and Hosted.NET
controls, Production builder and WMSII. Some features are not included into the
first release but were not declared deprecated.