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

A closer look at the Sales Header table (36)


For the main tables that are involved, let's take a look at the relationship between the Sales Header table (36) and the Sales Line table (37). Don't worry about the tables related to the FactBoxes; as we go through the Sales Header and the Sales Line tables, we'll see that figuring out the FactBoxes is a piece of cake.

Go back to Table Designer for Table 36 and let's take a deeper look at the composition of this table. Find Table 36 and click on Design to access Table Designer:

Table Designer has the following columns:

  • Enabled: You can define whether to enable a field or not on the table level.

  • Field No.: This is a unique ID for this particular field for that particular table.

  • Field Name: The name you want to give to this field. DO NOT assign a "developer" field name. For example, if you want to add a field called Customer Name, don't put it as CustName. Put it as Customer Name. The reason is because the pages and reports will use the field names...