Chapter 1: Architecture

CHAPTER 1: ARCHITECTURE
Objectives
The objectives are: • • • • • • Describe the basic features of Microsoft Dynamics® AX 2012. Review basic form navigation. Review the architecture of Microsoft Dynamics AX 2012. Describe the options for making development changes in Microsoft Dynamics AX 2012. Describe the theory of Model Driven Architecture in Microsoft Dynamics AX 2012. Review licensing and configuration.

Introduction
Microsoft Dynamics AX 2012 is a customizable, multiple-language, and multiple-currency Enterprise Resource Planning (ERP) solution. Microsoft Dynamics AX excels in: • • • • Manufacturing. E-business. Wholesale. Services industries.

Microsoft Dynamics AX is a completely integrated solution and is web-enabled and supports Microsoft® SQL Server®. With customizable source code, the solution can be modified however and whenever it is necessary.

Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement

1-1

Development I in Microsoft Dynamics® AX 2012

Features of Microsoft Dynamics AX
Microsoft Dynamics AX is a unique and powerful solution that contains functional and development environment features, which include the following: • Functional features o o o o o • Single database architecture is used for all companies in the organization. Highly integrated design between functional areas such as resource planning, sales, and manufacturing. Dimension-based system for all modules. Advanced features such as Forecasting and Master Planning are available. Multi-currency and Multi-language capabilities.

Development environment features o o o o o Microsoft Dynamics AX MorphX is an integrated development environment (IDE) for developing in Microsoft Dynamics AX. Visual Studio is an alternative development environment for web, report and managed code development. The Application Object Tree (AOT) provides a uniform and compact viewing repository. Drag-and-drop functionality is supported for many programming tasks. Projects help organize and track customized applications in Microsoft Dynamics AX.

Client Workspace
The client workspace is the standard rich client interface that an end-user uses. The workspace consists of various components:

Navigation Pane
The Navigation pane is the menu on the left side of the screen that shows all of the modules the current user has access to.

Content Pane
The content pane displays role centers, list pages and area pages. • Role centers display specific data, reports, alerts, and common tasks associated with a user's role in the organization. The role center is displayed when an end-user opens the application or goes to Home in the Navigation pane. List pages display lists of data. They are optimized to view and search through a list of records and act on information.

1-2

Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement

At the top of the screen is the Action Pane that contains buttons to open other forms and take actions related to the selected customer. Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-3 . To create a new customer.1 WORKSPACE Customers List Page In the Navigation pane. In the center of the form is a grid that displays a list of customers. They are grouped logically to make it easier for end-users to find what they need.Chapter 1: Architecture • Area pages display all menu items relevant to the module selected in the Navigation pane. On the right are FactBoxes that show data related to the selected customer. click Accounts Receivable > Common > Customers > All customers. This brings up a list of all customers in the system. A new form opens where you can enter data for the new customer. Fields with a red wavy line are mandatory. FIGURE 1. click New > Customer in the Action Pane.

The client application allows users to connect to the server to access business logic and use the data in the database. (Application elements are explained in the following lesson) An Application Object Server (AOS) is a service that runs most of the business logic. This runs continuously on a central server. Three-Tier Architecture Three-tier architecture is defined as having a separate database. Doing this sorts the data by customer account number order.2 CUSTOMER LIST PAGE Architecture Microsoft Dynamics AX has a three-tier architecture. FIGURE 1. • 1-4 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement . It also houses the model store that contains the application elements. and used by. the Microsoft Dynamics AX application. The server runs the application business logic. In Microsoft Dynamics AX the three tiers include the following: • A SQL Server Database that houses the data entered into. server and client where: • • • The database stores the data. click the field header of the Customer account field.Development I in Microsoft Dynamics® AX 2012 In the grid on the list of customers.

Integration to other applications or to third party organizations might require integration solutions such as web services. There are two versions of SharePoint that can be used.3 THREE TIER ARCHITECTURE Extended Architecture Several other components of the Microsoft technology stack are used in a typical deployment. Business Intelligence (BI) components such as Key Performance Indicators use Online Analytical Processing (OLAP) cubes which are delivered by SQL Analysis Services (SSAS). There are various clients available including the Microsoft Dynamics AX rich client and Enterprise Portal. Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-5 . FIGURE 1. SSAS is a component included in SQL Server. The Enterprise Portal and Role Pages are hosted in SharePoint. SSRS is a component included in SQL Server.Chapter 1: Architecture • The Client application is the user interface through which an enduser accesses Microsoft Dynamics AX. Microsoft SharePoint Server 2010 is a product that can be purchased to provide extended collaboration and content management tools. Window SharePoint Foundation 2010 is a free download. Reports are delivered by SQL Reporting Services (SSRS).

4 EXTENDED ARCHITECTURE SQL Server Databases Microsoft Dynamics AX Database The Microsoft Dynamics AX database is an Online Transactional Processing (OLTP) database that stores all the business data in SQL tables. The SSAS database is replicated from the OLTP database in a database format that is optimized for fast reporting and analysis. FIGURE 1. Business Intelligence (BI) Databases Some BI components of Microsoft Dynamics AX also require you to use SSRS and SSAS. 1-6 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement .Development I in Microsoft Dynamics® AX 2012 The following image describes a typical system architecture that includes other components of the Microsoft technology stack. This database also stores all of the metadata and application code in the Model Store.

net business connector. Enterprise Portal pages are displayed through a web browser. A subset of functionality and reports are available on the portal. Multiple AOS's can be installed to spread the processing load over multiple servers. End-users can use another application as the user interface that interacts with the AOS through the . Developers can access the developer tools through the MorphX IDE in the Microsoft Dynamics AX client or through Visual Studio Tools in Visual Studio. Web services: It is a web service endpoint.net and legacy applications. Most forms displayed in the rich client are designed by using the MorphX development environment. specialized applications written in .net Business Connector. Other Applications can be used as a client to the Microsoft Dynamics AX application. Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-7 . Session management: It manages client sessions. Security: It enforces security to manage access to data and functionality. Examples include mobile applications.NET Business Connector is a client that has no user interface. Microsoft Office® can be used as a client to access the Microsoft Dynamics AX application and data. The AOS is where most of the business logic is executed. It is designed for other applications to access the Microsoft Dynamics AX business logic. Some of the most important tasks include: • • • • X++ runtime: It runs the X++ code which provides most of the business logic in Microsoft Dynamics AX. Office add-ins are available out-of-the-box for Microsoft Excel and Microsoft Word. Role center pages are SharePoint pages that are displayed within a rich client form. The . Applications can be integrated using methods such as web services or the .Chapter 1: Architecture Application Object Server The Application Object Server (AOS) is the Microsoft Dynamics AX application server. The AOS performs many tasks. This improves performance in larger implementations. Clients Microsoft Dynamics AX Rich Client is the primary client to access Microsoft Dynamics AX functionality. SQL reports are called from the rich client by using the report viewer control.

Web Services Web Services are hosted within IIS. Development Environments The Microsoft Dynamics AX application is built of elements that are stored in the model store in the SQL Service database. Role Centers require the Enterprise Portal regardless of whether they are viewed through the web browser or the Microsoft Dynamics AX Windows Client. Classes and Methods are code objects that define business logic. the AOS generates a call to the Help server to display the Help pages. When a user accesses Help from within the rich client. Enterprise Portal and SharePoint IIS is required to host the Enterprise Portal framework within SharePoint. For example. the following element types make up part of the application: • • • Fields and Tables define data structure. Help Server Microsoft Dynamics AX Help files are hosted through IIS.Development I in Microsoft Dynamics® AX 2012 Other Components Internet Information Server (IIS) IIS is a web server that delivers content such as web pages. The AOS is the web service endpoint that provides the data that is served to other applications by IIS in a standardized format. 1-8 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement . Object-oriented design and Inheritance are key concepts that form the basis of the application. The Application Object Tree (AOT) provides a visual representation of the elements that comprise the application. Forms and Menus define how a user interacts with the application.

Blocked is an enum that gives the user only two options (yes or no) as to whether a customer account is on hold. For example. o Tables contain a group of associated fields. This is also referred to as the MorphX IDE and is accessed through the developer workspace in the Microsoft Dynamics AX client. left justified and is mandatory. Forms define the layout of all of the forms. Fields on a table contain individual pieces of data. AccountNum contains the customer account number. These are predefined text values that are referenced by an integer value in the database. These are presented to the user as a fixed list of options. For example. Base Enums are enumerated text data types. For example the CustTable contains fields relevant to customers. Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-9 . Extended data types define a data type and extended properties. There are various basic data types such as a string. A white paper titled "Selecting the Best Development Technology for your Application Development Scenario AX2012" is available for download on MSDN. date. Fields on a table inherit properties from extended data types. Application Object Tree A full definition of all the element types in Application Object Tree (AOT) can be found in the development training material and developer Help files. Microsoft Dynamics AX Integrated Development Environment (IDE). Forms are used to view data in the Microsoft Dynamics AX client. time and enum. The development environments that can be used with Microsoft Dynamics AX 2012 include: • • Microsoft Visual Studio. o o • • Classes contain code that is used in the application. AccountNum is a string extended with properties including a length of 20 characters. For example.Chapter 1: Architecture Model elements can be modified or added using a development environment. integer. Some of the root element types include: • Data Dictionary contains objects that define basic data structure.

Tools. This makes it easier to manage multiple languages and to adapt to company specific language. This label code is used in various places throughout the application. All text presented in the client displays the translation of a label code. The label codes usually are reused wherever the exact same text is used with the same meaning.Development I in Microsoft Dynamics® AX 2012 • • Visual Studio Projects display any development projects created in Visual Studio. including the label editor and label wizard. are available within the MorphX development environment to add or change label files. All label codes are already translated into all other languages in which Microsoft Dynamics AX is available. • • 1-10 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement . Menus define forms and reports that appear in the menu in the Microsoft Dynamics AX rich client. It is used on field names and menu items displayed on forms such as the Sales Order Header form. FIGURE 1. they will see the Spanish translation wherever this label code is used. Developers can create new label files to translate label codes into other languages or customer specific terminology. If an enduser opens the application in Spanish. This label code is translated as "Entrega directa" in the Spanish label file.5 AOT DISPLAYED IN THE DEVELOPER WORKSPACE Labels Labels are used to provide the language text that end-users see when using the application. As an example: • The label code @SYS78211 is translated as "Direct delivery" in the English-US label file.

forms and menus can be performed by using drag-and-drop techniques with little or no coding. Common operations such as building or modifying tables. This is the most commonly used development environment. X++ Tools X++ is the object-oriented programming language that is used in the MorphX development environment. You can access the MorphX IDE from the Microsoft Dynamics AX client. It supports color-coding and allows to look up and select various objects such as method names and enumeration values as you type. and incorporates SQL data manipulation statements.Chapter 1: Architecture MorphX IDE The MorphX IDE is accessed through the Developer Workspace which provides access to the AOT and other developer tools. and ERX ER data models. UML object models. The Table browser displays data from all fields in a selected table. X++ is the programming language that is used in the MorphX IDE to write more advanced business logic. The Debugger is an application used by developers to step through X++ code to help resolve code errors. Click the Windows menu in the command bar and select New Developer Workspace. The table browser can be used to run SQL statements. Some of the tools available include: • The X++ Code Editor is a text editor used to write X++ code. Alternatively you can use the shortcut keys Ctrl+Shift+W. It is used to make changes and add to the application. A full list of developer tools in the MorphX development environment can be found in the developer help documentation. The Reverse Engineering tool enables you to visualize data and classes in Microsoft Dynamics AX by creating UML data models. • • • Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-11 . X++ has C#-like syntax.

most Enterprise Portal web development and any managed code development.6 X++ CODE EDITOR Visual Studio The Visual Studio development environment is integrated through Visual Studio Tools for Microsoft Dynamics AX (Visual Studio Tools) and it supports managed code. This includes creating and customizing SSRS reports. Some development scenarios must take place in Visual Studio. Close integration between MorphX and Visual Studio means developers can take advantage of the benefits of each development tool and work in the environment that best suits their development scenario. 1-12 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement . FIGURE 1. It should be regarded as a development and testing tool.Development I in Microsoft Dynamics® AX 2012 NOTE: Extreme care must be taken when updating records in the table browser. It is always better practice to update data from the Microsoft Dynamics AX client.

Chapter 1: Architecture The Application Explorer is available within Visual Studio. you can group all your modifications in to a development project.7 APPLICATION EXPLORER IN VISUAL STUDIO Development Projects While developing in Microsoft Dynamics AX. Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-13 . Model Driven Architecture Microsoft Dynamics AX is designed with a unique layer and model structure that separates and controls the updates and modifications made in the application. Now any elements from the AOT can be dragged in to this project. This creates a reference to the element. This gives developers the ability to browse AX metadata. The Application Explorer displays information that is similar to the AOT in the MorphX IDE. To create a new development project. FIGURE 1. To create a new shared project: • • Right-click the Shared node and select New > Project. Give the project a descriptive name and then double-click it to open it. click the project icon in the development workspace. Visual Studio projects are displayed in the AOT and are stored in the Microsoft Dynamics AX model store in SQL server. or press Ctrl-Shift-P. Private projects are visible to the user creating them and shared project are visible to everyone. This structure provides a powerful and flexible architecture for developing business logic. Modifying elements in the project is the same as modifying them directly in the AOT.

FPP There are three layers available to partners and ISVs. 1-14 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement . GLP FPK. ISP VAR. This includes the core application and the localization for most countries. Layers Application object layers hold all elements that are displayed in the AOT.Development I in Microsoft Dynamics® AX 2012 The key benefit of the layer and model structure is that it lets developers change and extend the functionality in Microsoft Dynamics AX while maintaining upgradability to new versions. the modification overshadows the element on a lower level. VAP Description Solution layer: Includes Microsoft endorsed industry solutions. There are three layers available only to Microsoft to deliver the base application. When you make an element modification on one level. only the top-level version of an application element is used. Layers are a hierarchy of levels in the application you can use to make modifications and additions without interfering with the application elements in the next lower level. Value Added Reseller layer: Includes multi-customer solutions developed by VAR's. SYP Description System layer: The standard application is developed in this lowest layer. When the application is compiled. (The xxP layer indicates the patch layer for each application object layer). GLS. SLP ISV. Each of these layers also has a patch layer making a total of sixteen layers. Independent Software Vendor layer: Includes generic or vertical solutions developed by ISV's. Globalization layer: Includes features developed for some countries that were not yet moved into the SYS layer. There are eight application object layers available. Layer SLN. Layer SYS. Feature Pack layer: Includes industry feature packs that are controlled by Microsoft.

8 APPLICATION LAYERS Benefits of Layers: Source Code Protection The elements in the standard implementation (SYS. Any customer specific changes to the ISV solution would be in a higher layer. ISV solution code is separated in a model within the ISV layer. The layers help protect the original source code and keep it separate from modifications. User layer: Includes installation specific functionality and customizations. CUP USR. USP Description Customer layer: Includes customer specific functionality. GLS. FPK layers) can only be changed or deleted by the Microsoft Dynamics AX Development team. Similarly. Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-15 .Chapter 1: Architecture There are two layers available to both partners and customers who have a license to access the AX source code. FIGURE 1. Layer CUS.

They also manufacture. Models help in situations where multiple ISV solutions or projects must operate together. Solution A is an advanced vertical solution for the production of food and drug products. • 1-16 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement . The same element can exist in a customized version in a model in a higher layer. New models are easy to create in the MorphX IDE and are applied when modifying or adding objects in the AOT. the upgrade tool would highlight that there is a change in the SYS layer to 40 characters and there is an existing change in the CUS layer to 30 characters.Development I in Microsoft Dynamics® AX 2012 Benefits of Layers: Faster and Easier Upgrades Upgrades and service packs contain changes in the lower layers where the base code resides. this solution adds a new field to the item table to store the government approval number. The developer would then have the option to keep the CUS layer change or delete the CUS layer and revert to the new field length in the SYS layer of the new release. installed. the 30 character length is used. An element can exist in exactly one model in a layer. These tools highlight elements that are modified in higher layers and therefore might require some action to merge the changes. Models are identified by a name and a publisher. If a company that uses Microsoft Dynamics AX requires 30 characters for their item numbers. the field length would be changed to 30 characters and the change saved in the CUS layer. The CUS layer is a higher layer so when the application is compiled. As an example: • • The item number is an extended data type that exists in the SYS layer. If in a future version. Models can be exported. This is stored in the ISV layer and in the model MEDICAL. They manufacture and sell medical products. including a version number. or uninstalled from the model store. This means that any changes by partners or customers are maintained throughout the upgrade. Following is an example: • A company has two lines of business. sell and service specialized equipment to produce medical products. and have a set of properties that can be changed. • Models A model is a logical grouping of elements within a layer. This architecture allows many solutions to co-exist within each layer. Among other things. This field is a string which is 20 characters in length. The item number data type now exists in both the SYS layer and the CUS layer. Powerful compare and merge tools are available to guide developers through the upgrade. Microsoft extends the length of the item field to 40 characters.

The combination of name and publisher make a unique model. the version number. Among other things.9 CREATING A NEW MODEL To change the current model. a full description. click the current model in the status bar.Chapter 1: Architecture • Solution B is an advanced vertical solution for managing the ongoing service of equipment which is sold to customers. You can use models to view the modifications to the item table made by all ISV solutions and easily see where each change originated. • Managing Models Models can be created in the development workspace by clicking on Tools > Model management > Create model. This is stored in the ISV layer and in the model SERVICE. Then you can enter the model name. which layer the model is in. FIGURE 1. and a shorter description. this solution adds a new field to the item table for the default service period. Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-17 . your company.

Rename the project to Dev1Training. Click Close on the infolog dialog. 2. your name in the publisher and Dynamics AX Development 1 training labs in the description. the Systems Developer. Challenge Yourself! Create a model called Dev1 and a development project called Dev1Training Step by Step 1. 3.1 . 4.Development I in Microsoft Dynamics® AX 2012 Lab 1. 5. Press Ctrl-Shift-P to open the development projects window. During the remainder of the course. Right-click the Shared node and select New > Project. and also make it easy to move the modifications to test and production systems later. any elements you modify or create should be added to this project. Click Tools > Model Management > Create Model.Create a New Model and Development Project In this lab you will create a model and a development project to keep your modifications organized. Enter Dev1 in the model name. 1-18 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement . He wants to be able to group all the elements he creates and modifies together in one place. Click OK. needs to make a number of modifications to the system. Scenario Isaac. 7. 6.

10 ACCESSING CONFIGURATION KEYS Each configuration key controls access to a specific feature.Chapter 1: Architecture Licensing and Configuration The basic security architecture in Microsoft Dynamics AX includes license codes and configuration keys. These keys ensure the Microsoft Dynamics AX solution is not cluttered with functionality companies do not use. and once it is enabled or disabled. License Codes License codes control the modules that can be used within Microsoft Dynamics AX. Configuration keys have descriptions to describe the functionality affected by enabling or disabling them. which do not store data. none of that functionality is available. Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-19 . Configuration Keys Configuration keys in Microsoft Dynamics AX control the functionality and features in the system. FIGURE 1. Each configuration key is attached to a license code. but are set to be temporary tables. the configuration key is unavailable. the feature is automatically added or removed in the user interface. The underlying tables attached to that configuration key still exist in the database. so if the license is not purchased. If a license code for a module is not purchased.

The course introduced important terms related to Microsoft Dynamics AX Development. This course also discussed the basic security architecture that includes License codes and configuration keys. and it also discussed the user interface and the different ways data can be presented in forms and reports. 1-20 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement .Development I in Microsoft Dynamics® AX 2012 Summary This course provided a high-level introduction to the Microsoft Dynamics AX architecture.

A bank file import format developed by a partner that can be used for several of their customers. _____ 3. Match the following modifications to the layer which they are. Which of these statements best describes models in Microsoft Dynamics AX? ( ) A view of the metadata within the MorphX IDE. b. _____ 1. c. ( ) A piece of X++ code. ( ) A logical grouping of elements within a layer. Microsoft Dynamics AX 2012 has a three-tier architecture. developed in. A new field on the item table required for a vertical solution developed by an ISV. ( ) A visual representation of objects. 1. or should be. A new label code specified on a field to better reflect a particular customer's terminology. CUS VAR SYS ISV 4.Chapter 1: Architecture Test Your Knowledge Test your knowledge with the following questions. _____ 4. a. The core customer table _____ 2. d. What are the three tiers and what is the purpose of each tier? 2. What client applications can be used to access Microsoft Dynamics AX 2012? (Select all that apply) ( ) Microsoft Dynamics AX Rich Client ( ) Internet Information Server ( ) Application Object Server ( ) Enterprise Portal 3. Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-21 .

What is displayed in the Application Object Tree? (Select all that apply) ( ) Tables ( ) Forms ( ) Menus ( ) Visual Studio Projects 6.Development I in Microsoft Dynamics® AX 2012 5. Which tools can developers use to write Microsoft Dynamics AX business logic? (Select all that apply) ( ) Microsoft Office ( ) Visual Studio ( ) MorphX IDE ( ) SQL Server 1-22 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement .

2.Chapter 1: Architecture Quick Interaction: Lessons Learned Take a moment and write down three key points you have learned from this chapter 1. 3. Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-23 .

c. c 1.the user interface through which an end-user accesses Microsoft Dynamics AX. a 4. This runs continuously on a central server. the Microsoft Dynamics AX application. and used by. d 3. b. What client applications can be used to access Microsoft Dynamics AX 2012? (Select all that apply) (√) Microsoft Dynamics AX Rich Client ( ) Internet Information Server ( ) Application Object Server (√) Enterprise Portal 3. developed in.Development I in Microsoft Dynamics® AX 2012 Solutions Test Your Knowledge 1.a service that runs most of the business logic. A new label code specified on a field to better reflect a particular customer's terminology. Which of these statements best describes models in Microsoft Dynamics AX? ( ) A view of the metadata within the MorphX IDE. ( ) A visual representation of objects. 2. CUS VAR SYS ISV 4. (Application elements are explained in the following lesson) Application Object Server . There are various clients available including the Microsoft Dynamics AX rich client and Enterprise Portal. It also houses the model store that contains the application elements. ( ) A piece of X++ code. d. Match the following modifications to the layer which they are. The core customer table b 2. A bank file import format developed by a partner that can be used for several of their customers. a. Client application . or should be. What are the three tiers and what is the purpose of each tier? MODEL ANSWER: SQL Server Database . A new field on the item table required for a vertical solution developed by an ISV. (•) A logical grouping of elements within a layer. Microsoft Dynamics AX 2012 has a three-tier architecture.houses the data entered into. 1-24 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement .

Which tools can developers use to write Microsoft Dynamics AX business logic? (Select all that apply) ( ) Microsoft Office (√) Visual Studio (√) MorphX IDE ( ) SQL Server Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement 1-25 .Chapter 1: Architecture 5. What is displayed in the Application Object Tree? (Select all that apply) (√) Tables (√) Forms (√) Menus (√) Visual Studio Projects 6.

Development I in Microsoft Dynamics® AX 2012 1-26 Microsoft Official Training Materials for Microsoft Dynamics® Your use of this content is subject to your current services agreement .

Sign up to vote on this title
UsefulNot useful