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

Defaulting an item description on the line table


Using the skills we've gained from defaulting values on the fields, we will now try defaulting the Description field from the Item table when the user enters a value in the Item No. field.

For the coding method, or the method that's more consistent with out of the box Dynamics NAV, the table we want to use is the Item table. The field we want is the Description field from the Item table.

A reason why the FlowFields method would not work in the Complaint Line table is that if we set the field to be a FlowField, we will need to set the Description field as non-editable. This will not work because the user should be able to type in their own descriptions as they are entering data in the complaint lines.