Microsoft Dynamics AX 2012 - Development Introduction Training - Part 1/3

1. Fabio Filardi
Dynamics AX Technical Architect
ffilardi@msbsgroup.com

2. Microsoft Dynamics AX 2012
Development Introduction
Features
Architecture
Data Dictionary
User Interface
X++ Intro
X++ Control Statements
Objects and Classes
Accessing the Database
Exception Handling

3. Features
Microsoft Dynamics AX 2012
 High flexibility;
 Microsoft Office look and feel;
 Integrated development environment for developing;
 Visual Studio integration;
 Uniform and compact viewing repository (Application Object Tree);
 Drag-and-drop functionality;
 Projects help organize and track customized applications.

4. ARCHITECTURE
Microsoft Dynamics AX 2012
Topics
 Three-Tier Architecture
 Client Workspace
 Development Environment
 Layers
 Models

5. Architecture
Microsoft Dynamics AX 2012
Three-Tier Architecture
Three-tier architecture is defined as having a separate database, server and client:
 The client application allows users to
connect to the server to access business
logic and use the data in the database.
 The server runs the application
business logic.
 The database stores the data.

6. Architecture
Microsoft Dynamics AX 2012
Extended Architecture - The following image describes a typical system architecture that includes other
components of the Microsoft technology stack:

7. Architecture
Microsoft Dynamics AX 2012
Client Workspace
The client workspace is the standard interface that an end-user uses and consists of various components:

8. Architecture
Microsoft Dynamics AX 2012
List Pages - The primary method of displaying data in Microsoft Dynamics AX. They can show lots of data
from many tables, in a number of formats. They have consistent designs and functions.

9. Architecture
Microsoft Dynamics AX 2012
Development Environments
The development environments (IDE) that can be used with AX 2012 are:
 MorphX IDE
 The most commonly used environment;
 Provides easy access to the elements with the Application Object Tree (AOT);
 Drag-and-drop techniques;
 X++ language.
 Microsoft Visual Studio
 Integrated through Visual Studio Tools for Microsoft Dynamics AX;
 Close integration between MorphX and Visual Studio;
 Creating and customizing SSRS reports, Enterprise Portal web development and any managed code
development.

10. Architecture
Microsoft Dynamics AX 2012
Development Environments
The following element types make up part of the application:
 Fields and Tables define data structure.
 Forms and Menus define how a user interacts with the application.
 Classes and Methods are code objects that define business logic.
Object-oriented design and Inheritance are key concepts that form the basis of the application.

11. Architecture
Microsoft Dynamics AX 2012
MorphX IDE

12. Architecture
Microsoft Dynamics AX 2012
Microsoft Visual Studio

13. Architecture
Microsoft Dynamics AX 2012
Layers
Application object layers hold all elements that are displayed in the AOT.
There are eight application object layers available. Each of these layers also has a patch layer making a total
of sixteen layers.
Microsoft-only:
 SYS/SYP: System Layer
 GLS/GLP: Globalization Layer
 FPK/FPP: Feature Pack Layer
Partners and ISV:
 SLN/SLP: Solution Layer
 ISV/ISP: Independente Software Vendor Layer
 VAR/VAP: Value Added Reseller Layer
Partners and Customers:
 CUS/CUP: Customer Layer
 USR/USP: User Layer

14. Architecture
Microsoft Dynamics AX 2012
Layers
Benefits:
 Source Code Protection
 Faster and Easier Upgrades

15. Architecture
Microsoft Dynamics AX 2012
Models
 A model is a logical grouping of elements within a layer.
 Models help in situations where multiple ISV solutions or
projects must operate together.
 An element can exist in exactly one model in a layer.
 New models are easy to create in the MorphX IDE and are
applied when modifying or adding objects in the AOT.

16. DATA DICTIONARY
Microsoft Dynamics AX 2012
Topics
 Application Object Tree
 Table Structure and Components
 Data Types
 Labels
 Projects
 Jobs

17. Data Dictionary
Microsoft Dynamics AX 2012
Application Object Tree
 The Application Object Tree is a tree view of all
application elements in Dynamics AX;
 Each branch node contains a different application
element type;
 Create or modify Microsoft Dynamics AX application
elements using drag-and-drop functionality;

18. Data Dictionary
Microsoft Dynamics AX 2012
Application Object Tree
Table Structure and Components
There are seven categories that define tables:
 Fields
 Field Groups
 Indexes
 Full Text Indexes
 Relations
 Delete Actions
 Methods

19. Data Dictionary
Microsoft Dynamics AX 2012
Application Object Tree
Data Types: Primitive and Extended
Primitive Data Types: Extended Data Types:
 String EDTs extend primitive data types or other EDTs.
 Integer
 Real The benefit of creating EDTs is the reuse of their
 Date properties.
 Time
 UTCDateTime A table field that is created based on an EDT will also
 Enum inherit properties from that EDT, and the properties of
 Container many fields can change at one time by changing the
 GUID properties on the EDT.
 Int64
 Boolean

20. Data Dictionary
Microsoft Dynamics AX 2012
Application Object Tree
Labels
Labels are used to provide the language text that end-users see when using the application. Label Editor
makes it easier to manage multiple languages and to adapt to company specific language:

21. Data Dictionary
Microsoft Dynamics AX 2012
Application Object Tree
Projects
Projects help organize and track customized applications, grouping all
your modifications in Microsoft Dynamics AX.
Private projects are visible to the user creating them and shared project
are visible to everyone.

22. Data Dictionary
Microsoft Dynamics AX 2012
Application Object Tree
Jobs
A job is a stand-alone block of code in Microsoft Dynamics AX that can be run from the X++ editor. Jobs are
useful for testing blocks of code before inserting them into methods or classes.