1. How to use Resource Materials to teach this course
As part of the Resource Materials there are several elements including; Student Online Companion Guide, Instructor Presentation (PPT), Test Your Knowledge Questions (TYKQ’s) , and Lab/Practices. All of these materials are for the instructor use, except for the Student Companion Guide, this is the students take away from this course.
Instructor Notes:
The slide deck for this course is the primary guide for the instructor this will correspond to the companion guide to some degree. However, the printed transcript may not align 100%. Suggestion would be to review this deck and polish it to fit your needs. Practice the labs and demonstrations ahead of time, add own content to add additional student value outside of the eLearning. However the two can be used in conjunction.
eLearning - You might choose to complement your classroom experience by leveraging various components of the eLearning for this course. If you look within the notes of the PowerPoint slide deck for this course, you’ll find the names of the various sections within the eLearning where each lesson and demonstration are covered. The eLearning will cover the following topics:

2. Timeline – Total Course Duration: 1.5 Hours
Module Description
Time to Complete
Introduction
1 Minute
Azure
6 Minutes
Application Object Server
4 Minutes
Database
3 Minutes
Wiki Help
Client
 6 Minutes
Visual Studio and X++ Compiler
 9 Minutes
7 Debugger
8 Visual Studio Team Services
10 Minutes
9 Lifecycle Services
9 Minutes
10 Trace Parcer
 11 Minutes
Timeline – Continued on next page

3. Timeline – Continued Module Description Time to Complete
11 Office Integration
11 Minutes
12 Batch Servers
5 Minutes
13 Reporting and Business Intelligence
8 Minutes
Total Class Presentation
1.5 Hours

4. Disclaimer: This courseware is provided “as-is”
Disclaimer: This courseware is provided “as-is”. Information and views expressed in this courseware, including URL and other Internet Web site references, may change without notice. Unless otherwise noted, the examples depicted herein are provided for illustration only and are fictitious.  No real association or connection is intended or should be inferred.  This courseware does not provide you with any legal rights to any intellectual property in any Microsoft product. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this courseware may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means or for any purpose, without the express written permission of Microsoft Corporation.
Copyright © 2016 Microsoft Corporation. All rights reserved.
 Microsoft®, Microsoft Dynamics®, Microsoft Dynamics® CRM 2015, Microsoft Dynamics® CRM Online, Microsoft® SQL Server® data management software, Microsoft Office® Outlook and Microsoft PowerPoint® are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

5. Architecture
Welcome to the course on Architecture.

6. Course Objectives Review Microsoft Azure features.
Review the AOS and database architecture.
Explore the Dynamics AX client and development environment.
Discuss Lifecycle Services (LCS).
Examine the Trace Parser.
Review batch servers.
Highlight reporting, BI and office integrations.
In this course we will:
Review Microsoft Azure features.
Review the AOS and database architecture.
Explore the Dynamics AX client and development environment.
Discuss Lifecycle Services (LCS).
Examine the Trace Parser.
Review batch servers.
Highlight reporting, BI and office integrations.

7. Azure
In this lesson, we’ll discuss Azure.

8. Azure Information
Azure provides a scalable, resilient and accessible environment for AX
Azure SQL Database (PaaS)
Azure VMs (IaaS)
Azure Blob storage
Azure Active Directory
Azure SQL Database (PaaS)
AX Database(s)
Azure VMs (IaaS)
AX Application Object Server(s)
Azure Blob storage
Virtual Machine and file storage
Azure Active Directory
User access management, Single-sign on
Dynamics AX users are imported from an organization’s Azure Active Directory, which can be connected to an on premise Active Directory.

9. Demonstration Log onto Azure subscription
Look at AX database in SQL Databases
Look at AX AOS VMs in Virtual machines
Look at AX Users in Azure Active Directory
Log onto Azure subscription
Look at AX database in SQL Databases
Look at AX AOS VMs in Virtual machines
Look at AX Users in Azure Active Directory

10. Application Server AOS
Provisioned to IIS on an Azure Virtual Machine using LCS
Connects to AX database on Azure SQL Database service
Client access via a web browser
The Application Object Server is now hosted on an Internet Information Services (IIS) Web Server.
The AOS communicates with the AX Database, which is hosted using Azure SQL Database service in the cloud.

11. Demonstration
Log onto Azure Subscription and view AX AOS VMs in Azure Virtual Machines
Show IIS and AOS Web App

12. Database
In this lesson we’ll look at Azure SQL Databases.

13. Databases Overview *Entity Store Primary DB Secondary DB
Read only workloads
Analytics workloads
Read/write workloads
Ex: Sales Order entry,
Print Invoices
Ex: KPIs & Tiles,
Operational Reports
Ex: Power BI reports
Predictive analytics
Real Time
Real Time
Near Real-time
The primary database contains all of the real-time read and write workloads, such as sales order entry. The secondary database can be spun up if needed. It also contains real-time data, however it is read-only data, such as an operational report.
Finally, the entity store database is a planned feature to be released. It will be a near-real time database that will be based on underlying data entities. This will be used for performing predictive analytics and connecting with power BI.
Minutes
Seconds
Primary DB
Secondary DB
*Entity Store

14. Wiki Help
In this lesson we’ll cover the AX Wiki

15. Wiki Help
Dynamics AX Wiki Help:
Searchable repository with labs and tutorials
Extensive documentation available
Organized by area
A plethora of information can be found on the Dynamics AX Wiki Help. Content is organized by focus area an is full searchable. The Wiki is regularly updating with new content for the new Dynamics AX.

16. Client
In this lesson we’ll learn about the Dynamics AX client.

17. Accessed using a web browser
Dynamics AX Client
Accessed using a web browser
Supported Browsers
Microsoft Edge
Internet Explorer 11 on Windows 7+
Google Chrome on Windows 7+ or Google Nexus 10
Apple Safari on Mac OSX or Apple iPad
The Dynamics AX client now runs using an internet browser and leverages web technologies such as Java, HTML5 and CSS.
Nearly all browsers are supported.

18. Navigation Concepts
This graphic shows the relationships between these various forms. Every users starts with a Dashboard. Dashboards contain links to workspaces which are highly productive forms. From the workspaces we get into the more fundamental task oriented forms as you can see here in this graphic. For example the detail pages, list pages and some of the transactions forms.
Let’s switch over to AX and I’ll show you some of these navigation concepts.

19. Demonstration Log onto AX environment using a supported web browser

20. Visual Studio and X++ Compiler
In this lesson we’ll take a look at Visual Studio and X++ Compiler.

21. Exclusive development environment X++ fully integrated
Visual Studio
Exclusive development environment
X++ fully integrated
Elements organized by model
Overlaying vs. Extension
The X++ language is fully integrated into the Visual Studio environment. As you’re writing code, you will see the familiar features of the Visual Studio code editor. For example, IntelliSense is displayed to help you as you write your X++ code. Navigate to methods and classes in the code editor using the navigation drop-down menus located at the top of the code editor window.
Elements in Dynamics AX are the objects that reside in the AOT in the Application Explorer. Some examples of elements are tables and forms. Collectively, the elements are what define the system and dictate what the users will see on the front end. Elements can be customized once they are added to a specific project or model.
A Dynamics AX model is a group or collection of elements that constitute a distributable software solution. A model is a design time concept. For example, there may be a warehouse management model, or a fleet management model. A particular model may contain multiple Visual Studio projects each containing a subset (or all) of elements from the originating model. However, a project may only be associated with one model.
A Dynamics AX package is a deployment unit that may contain one or more models. In addition to elements, includes model metadata, which is the description data that defines the properties and behavior of the model. A package can be exported to a file, which can then be deployed into a staging or production environment.

22. Compiler Generates managed code (MSIL)
Utilizes maximum memory and cores
Performs telemetry
Best Practice framework
For Dynamics AX, the X++ compiler has been rewritten from scratch. No backward-incompatible changes have been introduced to X++ except where required by structural changes to the product. A few language enhancements have been added.
A new X++ best practice tool has also been implemented. It allows the addition of user-defined custom rules.
In Dynamics AX the standard compilation unit for X++ is the same as for other .NET languages such as C#. If any method on a Dynamics AX model element (class, form, query etc.) fails to compile, the whole compilation fails.
Everything is generated in MSIL managed code by the compiler.
Recommend 16GB memory for a full build; compiler will use all resources available for faster compiles.
IgnoreList – part of metadata, constrains entries for artifacts that the compiler will not compile in detail. Should be useful during upgrades scenarios.
Best practice errors or violations are outputted when compiling. You have the ability to turn these off or author your own best practice rules for the compiler to use as well.

23. Demonstration Basic layout of VS development environment
Model and classic view in AOT
Creating a new models
Compiler – run a build on a project
Note best practice framework
Note options for Development (Show line number, etc)
Basic layout of VS development environment
Model and classic view in AOT
Creating a new models
Compiler – run a build on a project
Note best practice framework
Note options for Development (Show line number, etc)

24. Debugger
In this lesson we’ll learn about the debugger in Visual Studio.

25. Debugging Code Visual Studio debugger Setting breakpoints
Navigate the call stack
To debug X++ code in Dynamics AX Preview, you will use the debugger in Visual Studio. The debugging process is similar to debugging any other application created with Visual Studio. For example, the standard tools for examining the application are available when your code is stopped at a breakpoint.
To debug X++ code, use the following procedure:
In Visual Studio, open the X++ code that you want to debug by right-clicking the code element from your project and choosing open.
Locate the line or lines where you want execution to stop, and set breakpoints in those lines. Do this by clicking in the left column of the code editor or by pressing F9 when the cursor is on the line. The red dot indicates that a breakpoint is set.
Save the code, then right click the element again and choose “Set as start up object”. Then, you can press F5 to build and run the code with the break point set.
*Autos window, info log

26. Debug Process Use “Start Debugging” or F5
Stopping the debugger
Autos window and Info Log
See variable values by hovering
Use “Start Debugging” or F5
On the DEBUG menu, click Start Debugging. It’s important that you run the application this way; otherwise, the program will not stop at breakpoints.
In the application, perform the action that causes the code you are interested in to run. Typically, this would be an action like displaying a form. Processing stops at the breakpoints that you have set.
Use the tools in Visual Studio to examine the application. For example, you can hover the pointer over variables in the X++ code to see their values. Use commands from the DEBUG menu to step through the code. Tools like the Autos window in Visual Studio will show important information about the state of the application.

27. Demonstration Open up a class, set breakpoints. Step through code
Review Autos Window and Info log
Open up a class, set breakpoints.
Step through code
Review Autos Window and Info log

28. Visual Studio Team Services Features
Team Foundation version control (TFVC)
Collaborate on code easily
Continuous Integration
Cloud based load testing
Centralized version control
Collaborate with colleagues on code with pull requests and code reviews, while defining and managing permissions to secure your repositories.
Catch quality issues early with continuous integration (CI) builds that compile and test your application automatically after any code change. 
Generate tests from regions around the world to simulate the scale of hundreds of thousands of users.
Visual Studio Team Services (VSTS) is the recommended source control system for Microsoft Dynamics AX.
In development topologies, multiple VMs cannot access the same VSTS project if they have the same machine name. VSTS uses the machine name for identification. If you are developing on local VMs downloaded from Microsoft Lifecycle Services (LCS), you may encounter issues.
To work around this, rename and reboot the machine before you start development. Then connect to VSTS.
After you do this you will also need to configure the SQL Server Reporting Server. To do that, change the SQL Server Name to (localhost) in the SQL Server Report Server Database connection string.

29. Demonstration Map a one-box VM to Visual Studio account
Map to one-box VM
In Visual Studio, connect to your account by going to Team explorer > Select Team Projects > Servers > Add.
Enter the URL to your team project. Click Close.
Make sure the VSTS account shows up. On the right, choose the project that you want to work on. Click Connect.
Now you need to create a workspace and map it to your VSTS account. Go to the Source Code Explorer and do this mapping:
Metadata > C:Packages
(*Demo necessary for this lesson?- do we have access to VSTS?)

30. Key Features of LCS Provision, manage and deploy environments
Monitor performance
Model business processes
Move data between environments
Download hotfixes and updates
Handle support tickets
Lifecycle Services will function as a one-stop place to manage your customers’ environments. Each customer that purchases Dynamics AX will receive 1 Lifecycle Services project. Customers will then add their partner or VAR as a user to the LCS projects. As a partner, you will be able to see one implementation project for each customer.
When you click a specific customer’s project, you can then began to manage their Dynamics AX environments. Some tasks that can be done include:
-Provision manage and deploy environments: Have a virtual machine deployed to Azure with the press of a button.
-Monitor environment health and troubleshoot performance issues: Environments are automatically deployed with tools that gather, index and surface events and performance counters up to LCS so you can monitor them from one place.
-Move data, code between your environments and also create solutions to provide on the Azure Marketplace
-Download updates and hotfixes: Service your environments by downloading and applying updates directly in LCS.
-Engage in cloud powered support: Create and handle support tickets and work items in an LCS dashboard. Partners can escalate items directly to Microsoft.

31. Business Process Modeler
BPM and Task Recorder
Access to both Global and Corporate Libraries
Gives ability to view and modify Process Hierarchies for core business processes
Sales Order Creation, Production Orders, etc.
Business Process Modeler
Able to capture and record user actions in the client
Can download or save in the LCS Libraries
Task Recorder
Business Process Modeler
Access to both Global and Corporate Libraries
Gives ability to view and modify Process Hierarchies for core business processes
Sales Order Creation, Production Orders, etc.
Task Recorder
Able to capture and record user actions in the client
Can download or save in the LCS Libraries

32. Demonstration Log onto LCS and review More tools in the LCS project

33. Trace Parser
In this lesson we’ll learn all about Trace parsers in AX.

34. Trace Parser Separate installation required Capture events
Viewing events
Timeline tab
X++ Call tree
Requires that you access the Dynamics AX environment as an administrator on the Dynamics AX instance. Any user can start and stop trace, but trace analysis is available only for administrators.
The Timeline tab has the following major components:
The Select Grouping drop-down allows you to group based on a variety of categories, such as Customer ID, Username, Session Name, etc. Groupings will display maximum and minimum timestamp of events, total number of events, and lowest event level within the grouping.
List of all events in a threaded or unthreaded view.
Property grid displayed for the selected event.
Timeline chart for all the selected events.
Filtering of events.
Session analysis notes.
Call tree view
By selecting the Call Tree tab, you can see the call tree for all X++ methods. The tab is shown below.

35. Demonstration Capture Trace Open Trace SQL View for Trace
The Trace parser can be downloaded from Connect. You will need to install it separately from Dynamics AX. After the Trace parser is installed, you will find it here:
C:\Program Files (x86)\Microsoft Dynamics AX Preview\Microsoft.Dynamics.AX.Tracing.TraceParser.exe
Capture events from the local installation of Dynamics AX.
If the Select Trace window isn’t already open, go to the File menu and click Open trace. In the Select Trace window, click Capture Events. After selecting your providers, click Start. The Trace Parser tool will start listening to all the providers and capturing the events. Capturing stops when you click Stop and Import.
Open an existing ETL (Windows Event) file that was captured using tools such as Logman.
Go to the settings gear and click trace, give it a name.
Click start trace, then create a PO –Procurement and Sourcing > All Purchase Orders, new, choose vendor, choose item and site.
Click stop trace.
Download trace (locally) or analyze trace (converted to db on server)

36. Office Integration
In this lesson, we will discuss the integrations available between office and AX.

37. Excel Integrations Excel Data Connector App Static Export to Excel
Generated Open in Excel
Lookups and data assistance
Workbook Designer
The Excel App is built using a new Apps for Office framework that provides a JavaScript-based web API for apps to communicate with the Office applications. The biggest advantage of using this new framework is that apps can run inside Excel on-premise (Win32), Excel Online (Office 365), Excel on the iPad, and other Excel apps in the future. The app leverages Odata feeds and allows inserting, updating, and deleting data, so users have the ability to publish back to AX.
Static Export to Excel provides a quick mechanism to get the data in grids on a form. The standard mechanism for triggering Export to Excel in Dynamics AX is via the Open in Microsoft Office menu. Static Export to Excel is also available via a right-click context menu on the grid.
“Generated Open” in Excel options are added to forms automatically by finding data entities that have the same root datasource as the form. The generated workbook will contain a single table binding that will have the data from that entity loaded. The Open in Excel experiences are listed under the Open in Microsoft Office menu.
To facilitate data entry, the Excel App provides lookups and data assistance. Date fields provide a date picker, enumeration (enum) fields provide a enum list, and relationships provide a relationship lookup.
Workbook Designer can be launched from AX and allows you to create workbooks by pulling in data from AX. We can leverage the data entity relationships to see related records. For example, we can design a workbook that shows car rentals by customer.

38. Other Office Integrations
SysMailer framework = one framework, multiple providers
Generate messages with Outlook
Microsoft Word
Template designer
Add fields, tables, label adjustments
workflows enabled via the Sys framework can generate an message (EML file) containing attachments for sending via Outlook or another client. Users can also opt to use a simple client provided in a dialog. Developer options: Add capabilities to a form
Microsoft Word supports integration to Dynamics AX as well. From the open from office menu on a form, you can select the option to open with Microsoft word.
Word leverages a template designer to which you can add fields and tables and make label adjustments.

39. Demonstration Demonstrate fleet management customers
In IE, navigate to Fleet Management > Customers > Customer.
Click Open in Microsoft Office > Open in Excel > Fleet Management Customers.
Open the generated workbook. The workbook contains the Excel Data Connector App, a binding to the Fleet Management Customer entity, and a pointer to the server it was generated from.
Click Enable editing to allow the Excel Data Connector App to load.
Customer data will be read from the OData service on the server and added to the table.
In IE, in the Customer form, click Edit (or type F2) and change the address of one of the customers.
Click Refresh in the Excel App.
Note that the changed address is shown in Excel.
In Excel, change the address of one of the customers.
Click Publish in the Excel App.
In IE, click Refresh (the button is in the top right of the form) or type Shift+F5.
Note that the changed address is shown in the Customer form.
In Excel, click the Settings button (the button with a gear symbol on it in the bottom-right corner of the Excel App). The Excel App has a settings dialog to allow the user to adjust the settings in the current workbook.
Note that the Server URL matches the start of the URL shown in IE.
In Excel, click the Message Center button (the button with a flag symbol on it in the bottom-right corner of the Excel App). The Excel App has a message center dialog to provide the user with information about what is happening within the Excel App.
Note that the data refresh and data publish operations are listed.

40. Batch Servers
In this module we’ll take a look at batch servers.

41. Tasks can be run as part of batch jobs
Batch Servers
Tasks can be run as part of batch jobs
Batch processing runs as a service
Assign groups to certain batch servers
Many tasks in Dynamics AX can be run as part of batch jobs. For example, batch jobs can include tasks for printing reports, performing maintenance, or sending electronic documents. By using batch jobs, you can avoid slowing down your computer or the server during typical working hours.
Batch processing is done via a service that runs on the AOS. Use batch groups to categorize batch tasks and run them on specific servers. The servers in your environment might have different software installed, or they might be available at different times of the day.
Batch groups are used to direct batch tasks to the most appropriate server. Tasks in the same batch job can belong to different batch groups. For example, server A is set up to print reports, and server B is set up to send electronic documents. You can use batch groups to make sure that reporting tasks are run on server A and electronic documents are processed by server B.

42. Demonstration Show the batch jobs form Show the batch groups form
Show batch jobs form
Show batch groups form

43. Reporting and Business Intelligence
In this module we will discuss reporting and business intelligence.

44. SSRS Reporting Services hosted in Microsoft Azure Compute service
Simplified development
Simplified administration
Enhanced report viewing
In Microsoft Dynamics ‘AX 7,’ reporting services are hosted in the Microsoft Azure Compute service. If you’re developing in a one-box environment, the services also run locally in the Azure compute emulator.
In a one-box environment, developers can modify, create, and preview reports, from end to end, in Microsoft Visual Studio A separate process isn’t required to add reports to the Application Object Tree (AOT) on the application server. Changes to reports that are packaged together with other solution updates are uploaded and deployed to the cloud only after development is completed in the local environment.
The enhanced report viewing experience for end users in the Dynamics ‘AX 7′ client is the same as the report preview in Microsoft Visual Studio. By pressing Ctrl+F5, you can build and preview the report in an Internet Explorer window. The report appears exactly as it would appear in the client.
SSRS reports offer built-in back-office document management capabilities, such as support, scheduled executions via batch, and print archive.
SSRS reports provide parameterized views and drill-through navigations to Microsoft Dynamics AX pages and other reports.
You can produce precision documents to comply with local regulatory business practices.

45. Power BI Cloud Service
Microsoft Power BI is a collection of tools and services that enables interactive visualizations and dashboards. Power BI is the tool that many users choose when they want to create interactive visualizations and self-service reports for Microsoft Dynamics ‘AX 7.’ You can access Power BI visualizations from PowerBI.com with a free account.
Power BI also allows developers to create their own visualization types using web technologies such as HTML5 and D3. The API also enables developers to incorporate these tiles in other web or mobile apps outside of Dynamics AX.

46. Power BI Integration Cloud and mobile access
Embed BI tiles in AX client
Content Packs
OData support
Dynamics ‘AX 7′ integrates with Power BI by being a first-class source of data to Power BI authoring tools such as Microsoft Excel. After reports are authored, they can be published to PowerBI.com for collaboration and mobile access. Although dashboards and reports can be used on PowerBI.com, they can also be pinned to the Dynamics ‘AX 7′ client to provide interactive visuals that are related business processes.
Pre-built Dynamics ‘AX 7′ content packs from Microsoft, and also from independent software vendors (ISVs) and partners, offer ready-made analytical dashboards and reports for industry verticals. Users can deploy these content packs from PowerBI.com.
Tiles and charts created in Power BI can be pinned in the AX client as well. As users view reports and visuals on PowerBI.com, they can drill back into the Dynamics ‘AX 7′ client to take action on trends and exceptions. Users see only data that is relevant to them, and that they have access to in Dynamics ‘AX 7.’
Securely connect to data entities in AX via the OData feed, which automatically enforces AX security. This means users will only see data from the BI embedded elements that they have access to see in AX itself.

47. BI Components In-memory, real-time Aggregate Measurements
Aggregate Data Entities
Programmatic access
KPI Modeling
In Memory - This option will leverage the In-memory Column store indexes of SQL Server database to deploy Aggregate Measurements
Aggregate measurements, similar to perspectives and Cubes from earlier versions of Microsoft Dynamics AX, enable you to model and consume aggregate data in Microsoft Dynamics ‘AX 7.\’ They are essentially star-schemas of modeled data. These measurements require aggregate dimensions, which can be modeled from tables, views or data entities.
Aggregate data can be consumed in building charts and other controls. Using the model driven approach, you have the ability to create data entities by directly referencing aggregate measurements and aggregate dimensions. These entities are referred to as Aggregate data entities. Aggregate data entities are read-only data entities used for reporting purposes in SSRS and Power BI.
Key Performance Indicators (KPIs) are a form of analytic controls that track organizational performance against the current status. KPIs are represented as tiles in a workspace or the dashboard.
KPIs that are modeled in Visual Studio can be modified in the Dynamics AX client. A user also has the ability to model new KPIs using the Dynamics AX client.
KPIs are defined using aggregate measurements; they can also be defined across companies.
The aggregate programming model enables a developer to consume aggregate data programmatically using either X++ or C# code. Data retrieved using the aggregate programming model can be used as a data source in forms.
Method expressions enable a developer to build rich expressions using aggregate data. Method expressions are an X++ class. KPIs can be modeled using method expressions, thereby eliminating the need to build MDX expressions.

48. Test Your Knowledge
1. Which of the following are features of Azure Active Directory? (Select all that apply)
Creating users and groups
Configuring web and native applications
Connecting to Azure SQL
Hosts the AOS (Application Object Server)
Which of the following are features of Azure Active Directory? (Select all that apply)
Creating users and groups
Configuring web and native applications
Connecting to Azure SQL
Hosts the AOS (Application Object Server)
Justification:
This statement is true. cAAD can be used to add users to the tenant as well as groups.
This statement is true. AAD can also be set up web or native client applications, which generate a client ID that can be used to integrate applications.
This statement is false. Azure Active Directory does not connect directory to Azure SQL; they are separate features of Azure.
This statement is false. The AOS is hosted in IIS (Internet Information Services) as a web application.
Related Lesson: Azure

49. Test Your Knowledge
2. TRUE or FALSE. The secondary database is automatically deployed in every environment.
True
False
TRUE or FALSE. The secondary database is automatically deployed in every environment.
True
False
Justification:
False: This statement is false. The secondary database may be spun up if chosen during the deployment process.
Related Lesson: Database

50. Test Your Knowledge
3. Which of the following are features of the X++ compiler? (Select all that apply).
Generates managed code (MSIL)
Utilizes maximum memory and CPU cores
Includes a Best Practice framework
Performs Telemetry
Which of the following are features of the X++ compiler? (Select all that apply).
Generates managed code (MSIL)
Utilizes maximum memory and CPU cores
Includes a Best Practice framework
Performs Telemetry
Justification:
This statement is correct. The code generated by the compiler is called managed code (MSIL).
This statement is correct. The compiler will utilize the maximum memory and CPU cores during the compiling process. This will allow for much faster builds.
This statement is correct. The compiler now includes a best practice framework. Best practices messages are shown in the Output tab. This feature may be turned on or off. A developer may also author their own best practice rules.
This statement is correct. The X++ compiler also performs telemetry.
Related Lesson: Visual Studio and the X++ Compiler

51. Test Your Knowledge
4. TRUE or FALSE. Trace parser is included with each Dynamics AX installation.
True
False
TRUE or FALSE. Trace parser is included with each Dynamics AX installation.
True
False
Justification:
False: This statement is false. Trace parser must be downloaded and installed separately. It may be downloaded on Microsoft Connect.
Related Lesson: Trace Parser

52. Test Your Knowledge
5. Where can Power BI visualizations be added or pinned in the Dynamics AX client?
On any form
Only on workspace forms with a tab page that has a Section Power BI subpattern applied.
Only the main dashboard page
Only on a form with a tab page that has a subpattern type of Image Preview.
Where can Power BI visualizations be added or pinned in the Dynamics AX client?
On any form
Only on workspace forms with a tab page that has a Section Power BI subpattern applied.
Only the main dashboard page
Only on a form with a tab page that has a subpattern type of Image Preview.
Justification:
This statement is incorrect. Adding Power BI tiles is currently only supported on Workspace forms.
This statement is correct. Power BI tiles can only be added to a Workspace form that includes a tab page with the Section Power BI subpattern applied.
This statement is incorrect. Power BI tiles cannot be pinned on the default dashboard home page currently.
This statement is incorrect. Power BI tiles are only supported on Workspace forms that include the tab page with the Section Power BI subpattern applied.
Related Lesson: Reporting and Business Intelligence

53. Test Your Knowledge
6. Where can the Excel Data Connector App be used? (Select all that apply).
In Excel for Windows, Excel Online (Office 365) and Excel for iPad.
Only for Excel Online (Office 365) and Excel for Windows
Only for Excel for Windows and the Excel app for iPad
Only for Excel for Windows
Where can the Excel Data Connector App be used? (Select all that apply).
In Excel for Windows, Excel Online (Office 365) and Excel for iPad.
Only for Excel Online (Office 365) and Excel for Windows
Only for Excel for Windows and the Excel app for iPad
Only for Excel for Windows
Justification:
This statement is correct. The Excel app can be used in both the Windows version of Excel as well as the online version of Excel in Office 365. The Excel app functionality is also supported within the Excel for iPad app on iOS.
This statement is not correct. While the Excel app does work in Excel Online and Excel for Windows, it is also supported by the Excel app for the iPad.
This statement is incorrect. The Excel app is supported by Excel for Windows and the iPad app; however, it is also supported in Excel Online (Office 365).
This statement is not correct. The Excel app does work with the Windows version of Excel, but it is not limited to only the on premise version.
Related Lesson: Office Integration

54. Test Your Knowledge
7. Which of the following is NOT a feature of Lifecycle Services (LCS)?
Deploy environments (virtual machines)
Monitor and troubleshoot performance of environments
Restart IIS and the AOS
Model business processes
Which of the following is NOT a feature of Lifecycle Services (LCS)?
Deploy environments (virtual machines)
Monitor and troubleshoot performance of environments
Restart IIS and the AOS
Model business processes
Justification:
This statement is incorrect. Deploying environments is a feature of LCS; therefore, this statement is not correct.
This statement is incorrect. Monitoring and troubleshooting performance of environments is a feature of LCs; therefore, this statement is not correct.
This statement is correct. Restarting IIS or the AOS is not supported directly through LCS. You perform this task on the actual environment in question.
This is incorrect. Power BI tiles are only supported on Workspace forms that include the tab page with the Section Power BI subpattern applied.
Related Lesson: Lifecycle Services