Book Image

Microsoft Dynamics NAV 2009 Application Design

By : Marije Brummel
Book Image

Microsoft Dynamics NAV 2009 Application Design

By: Marije Brummel

Overview of this book

Dynamics NAV 2009 is an Enterprise Resource Planning (ERP) software product from Microsoft that can be used for variety of business needs. It is part of the Microsoft Dynamics family, and intended to assist with finance, manufacturing, Customer Relationship Management, supply chains, analytics, and electronic commerce for small and medium-sized enterprises. This book is a focused tutorial on Microsoft Dynamics NAV application development, so you can develop complete applications and not just application outlines. It will show NAV developers how to create different kinds of applications. Different kinds of application are vital in different industries like fashion, automobile, retail, books (education), and other industries. It starts off by introducing the supply chain that you will be using throughout the book. You will implement the Microsoft Dynamics NAV ERP suite and learn how it is set up and customized for various industries. You will be able to customize Dynamics NAV to suit the different aspects of a business such as Financial Management, Relationship Management, Production, Jobs, Trade, Storage, Logistics, and so on. The book will take you through these Microsoft-designed application features and show you how to customize and extend them safely. Thus, you will be able to create a structure of your own in Microsoft Dynamics NAV.

Related Content you might be interested in

Current Title:

Small book image
Microsoft Dynamics NAV 2009 Application Design
Marije Brummel
Jun, 2010 | 496 pages
No titles found
Table of Contents (13 chapters)
Preface
Preface
Free Chapter
1
Chapter 1: Introduction to Microsoft Dynamics NAV
Chapter 1: Introduction to Microsoft Dynamics NAV
Versions and history
What is this book about
Setup versus customization
The beauty of simplicity
Structure of this book
The Role Tailored concept
The building blocks
Data model principles
Summary
2
Chapter 2: A Sample Application
Chapter 2: A Sample Application
Fit-gap analysis
Getting started
Designing a journal
The posting process
Invoicing
Navigate
Summary
3
Chapter 3: Financial Management
Chapter 3: Financial Management
Chart of accounts
Customizing financial management
Integrating with financial management
Summary
4
Chapter 4: Relationship Management
Chapter 4: Relationship Management
How companies work
Customizing relationship management
Summary
5
Chapter 5: Production
Chapter 5: Production
What is production?
Basic production principles
Getting started
Vertical industry implementation
Summary
6
Chapter 6: Trade
Chapter 6: Trade
The process
Sales and purchasing
Inventory management
Warehouse management
Reservations
Trade in vertical industries
Summary
7
Chapter 7: Storage and Logistics
Chapter 7: Storage and Logistics
How to read this chapter
The storage application
The logistics application
The invoicing application
Add-on flexibility
Summary
8
Chapter 8: Consulting
Chapter 8: Consulting
The process
Getting started
Changing jobs
Summary
9
Chapter 9: Interfacing
Chapter 9: Interfacing
Interface types
Interfacing technologies
Standard application interfaces
Interface methodologies
Interfacing into the future
Summary
10
Chapter 10: Application Design
Chapter 10: Application Design
Application lifecycle
Version and object management
Development methodology
The project
Summary
11
Thank you for buying Microsoft Dynamics NAV 2009 Application Design
Thank you for buying Microsoft Dynamics NAV 2009 Application Design
Appendix: Installation Guide
Appendix: Installation Guide
Licensing
Installing the objects

Navigate

We have now covered everything that is necessary for our Squash Court application to run but there is one special function of Microsoft Dynamics NAV that needs changing when we add new documents and ledger entries—the Navigate function.

The functionality was already discussed in Chapter 1. The object is a single page (344) in the application that requires two changes.

FindRecords

The first function we change is FindRecords. This browses though the database finding all possible combinations of document no. and posting date.

FindRecords()
...
// Squash Ledger Entries
IF SquashLedgEntry.READPERMISSION THEN BEGIN
  SquashLedgEntry.RESET;
  SquashLedgEntry.SETCURRENTKEY("Document No.",
    "Posting Date");
  SquashLedgEntry.SETFILTER("Document No.",DocNoFilter);
  SquashLedgEntry.SETFILTER("Posting Date",PostingDateFilter);
  InsertIntoDocEntry(
    DATABASE::"Squash Ledger Entry",0,
    SquashLedgEntry.TABLECAPTION...
Previous Section
End of Section 7
Next Section