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

Function libraries and interfaces

Not every function in Microsoft Dynamics NAV has a clear owner. In some cases, we have a function that can be accessed using simple variables that perform some calculation or a small piece of business logic.

These functions can be put in function libraries or interfaces. By doing this, it is easy for other developers to reuse them.

Examples of function libraries can be string manipulations or date functions. Microsoft Dynamics NAV does not have a lot of built-in functions for this, and many developers have created their own collection of functions through the years.

An Interface is a reusable component that can be accessed from anywhere in the application. A very good example of what could and should be an interface is the function called DateNotAllowed in Codeunit 11, Gen. Jnl.-Check Line:

IF (AllowPostingFrom = 0D) AND (AllowPostingTo = 0D) THEN BEGIN
  IF USERID <> '' THEN
    IF UserSetup.GET(USERID) THEN BEGIN...
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