Book Image

Getting Started with Dynamics NAV 2013 Application Development

By : Alex Chow
Book Image

Getting Started with Dynamics NAV 2013 Application Development

By: Alex Chow

Overview of this book

So, your company has made the wise decision to use Dynamics NAV as its main business software for all its enterprise resource planning. Dive in and learn the ins and outs of the software from a development standpoint and unlock the software's full potential.The book will walk you through creating an application from start to finish. Once you know how to create a working application that users can access, you will have the knowledge and the resources needed to create other applications based on the tutorials covered in this guide.You will start by obtaining a free trial version of Dynamics NAV and then be introduced to the world of analyzing and deriving user problems into a requirements list. Finally, you will be shown how to use the software to knock out these requirements. You will learn everything you need in order to begin creating your own applications, from translating the user's requirements to creating and modifying your system applications. Use Dynamics NAV's capability to create an application and address the user's needs, while also learning best practices and simple solutions. "Getting Started with Dynamics NAV 2013 Application Development" will help you on your way to becoming a great developer!
Table of Contents (17 chapters)
Getting Started with Dynamics NAV 2013 Application Development
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Creating the Complaint Line table


Alright! Let's take a look at our requirement list and see what we've accomplished so we can get them marked off as follows:

The next thing on our requirement list will require a different table. How do we know this? Because we've thoroughly looked through the Sales Header and Sales Line tables and we've seen what information should go where.

The requirement list says that we need to have one or more items per incident. This should be the leading indicator for you to know that the information related to the item belongs in the line table.

In Object Designer, create a new table called Complaint Line with the field Document No.. The Data Type should be Code with Length as 20; again, this should be exactly the same as the No. field on the Complaint Header table. As you may have guessed, these two tables will be related. When you save it, save the table as 50001.

Set up the table relation to the Complaint Header table on the Document No. field. The reason we want...