Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
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
Learning Dynamics NAV Patterns

You're reading from   Learning Dynamics NAV Patterns Create solutions that are easy to maintain, are quick to upgrade, and follow proven concepts and design

Arrow left icon
Product type Paperback
Published in Sep 2015
Publisher Packt
ISBN-13 9781785284199
Length 214 pages
Edition 1st Edition
Arrow right icon
Authors (2):
Arrow left icon
Marije Brummel Marije Brummel
Author Profile Icon Marije Brummel
Marije Brummel
Mark Brummel Mark Brummel
Author Profile Icon Mark Brummel
Mark Brummel
Arrow right icon
View More author details
Toc

Table of Contents (9) Chapters Close

Preface 1. Chapter 1: Introducing Dynamics NAV Patterns and Software Architecture 2. Chapter 2: Architectural Patterns FREE CHAPTER 3. Chapter 3: Design Patterns 4. Chapter 4: Building an Example Application Using Patterns 5. Chapter 5: Coding Best Practices 6. Chapter 6: Anti-patterns and Handling Legacy Code 7. Chapter 7: Building Solutions Using Patterns 8. Thank you for buying Learning Dynamics NAV Patterns

Step four – Documents

When designing applications in Microsoft Dynamics NAV, the Documents allow us to implement a functional workflow that resembles the traditional paper flow in a company. From a pure accounting and auditing perspective, we can run the application without Documents and have the same entries as a result in the database.

Documents act as containers of functionality for end users to be able to work with the application in a human way.

Let's add a Document in our example application and see how we can connect this to our journal during a posting process.

Implementing a Document

To implement a Document we must follow the following Diagram. Remember that the Document Type is optional.

For our Example Document the table structures look as displayed in the following screenshot:

We also need a set of page objects. A list and a card page, as created for the Master Data, and a page for the lines as...

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