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.
Table of Contents (13 chapters)
Preface
11
Thank you for buying Microsoft Dynamics NAV 2009 Application Design

Interface types

When discussing an interface we usually start with the technology, but before that, some other basic questions need answering such as the following:

  • Does it need to import, export, or both?
  • Is it started manually or automatically?
  • Is the interface timer or event driven?

Let's discuss these questions.

Import and export

The first question is if the interface should only export data from Microsoft Dynamics NAV or if it would also import data to the system which then needs to be processed.

When importing and exporting, the data process can be started manually by an end-user using data pulling or data pushing. The interface can also be event or timer driven.

Manual

When an interface is manual, the first application has an export process and another application has an import process. The end-user first manually starts the export process and then manually starts the import process in another application, usually saving the data...