Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
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

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...

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 €18.99/month. Cancel anytime