Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Getting Started with Dynamics NAV 2013 Application Development

You're reading from   Getting Started with Dynamics NAV 2013 Application Development Using this tutorial will take you deeper into Dynamics NAV from a developer's viewpoint, and allow you to unlock its full potential. The book covers developing an application from start to finish in logical, illuminating steps.

Arrow left icon
Product type Paperback
Published in May 2013
Publisher Packt
ISBN-13 9781849689489
Length 230 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Alex Chow Alex Chow
Author Profile Icon Alex Chow
Alex Chow
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Getting Started with Dynamics NAV 2013 Application Development
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Getting Dynamics NAV 2013 on Your Computer – For (Almost) Free FREE CHAPTER 2. Getting Familiar with Dynamics NAV 2013 3. Exploring the Data Structure and Basic Layout of Dynamics NAV 4. Determining a Task List 5. Finding Similar Functions for Inspiration 6. Creating the Application – Tables 7. Creating the Application – Pages and Reports 8. Extending Our Application 9. Dynamics NAV Modules to Address the Specific Needs of Your Business Additional Resources and Conclusion 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.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image