Book Image

Learning MS Dynamics AX 2012 Programming

By : Mohammed Rasheed, Erlend Dalen
Book Image

Learning MS Dynamics AX 2012 Programming

By: Mohammed Rasheed, Erlend Dalen

Overview of this book

<p>This tutorial has been carefully structured to guide you through the basic features of AX development and get you started as quickly as possible. With this book, you will soon be able to develop and maintain comprehensive management solutions to enhance your Dynamics AX 2012 application's performance. Starting with a tour of the development environment, you'll gain a deep understanding of Dynamics AX tools and architecture, before getting to grips with X++ for deeper customization. You will also learn how to search, manipulate, and integrate data.</p> <p>The practical examples in this book take you through sample AX development projects and help you learn to create forms, reports, menu&nbsp; items, menus, and navigation pages. The book also helps you work with MorphX. By the end of this book, you will have a better understanding of the inner workings of Microsoft Dynamics AX—making your development simpler and faster, and your applications fast, reliable, and robust.</p>
Table of Contents (21 chapters)
Learning MS Dynamics AX 2012 Programming
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Links
Debugger
Index

Views


In AX, views are objects that are used to retrieve data from the database and stored in the memory on the layer in which the view is instantiated. The views are actually stored as database views on the SQL server. This means that there are potentially great performance benefits of using views compared to using an equivalent query. This depends on the complexity of the query but, in general, the performance benefits of using a view compared to a query will increase and the complexity of the query will increase.

Views can be used throughout AX in all places where tables can be used; this includes forms, queries, and reports in the X++ code.

Note

Views in AX can never be used to write data; they are used only to read data from the database. This differs from the SQL implementation that has write back possibilities for views.

Creating a view

We will now create a view that consists of car ID, car brand, car model, customer's name, from date, and to date.

  1. First, we locate the Views node under...