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 now! 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
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Dynamics NAV 2013 Application Design

You're reading from   Microsoft Dynamics NAV 2013 Application Design Customize and extend your vertical applications with Microsoft Dynamics NAV 2013

Arrow left icon
Product type Paperback
Published in Sep 2014
Publisher Packt
ISBN-13 9781782170365
Length 504 pages
Edition 2nd Edition
Languages
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 (12) Chapters Close

Preface 1. Chapter 1: Introduction to Microsoft Dynamics NAV FREE CHAPTER 2. Chapter 2: A Sample Application 3. Chapter 3: Financial Management 4. Chapter 4: Relationship Management 5. Chapter 5: Production 6. Chapter 6: Trade 7. Chapter 7: Storage and Logistics 8. Chapter 8: Consulting 9. Chapter 9: Interfacing 10. Chapter 10: Application Design 11. Installation Guide

The process

The two main processes for Microsoft Dynamics NAV partners are implementing new projects and providing services such as supporting and upgrading to existing customers. A third process is selling infrastructure and assembling computer systems but this is an extra service, not the core business.

To support the projects (jobs), the company needs people, software licenses, and hardware. The people (resources) need to be carefully planned on the projects as they are the least flexible part of the company. Hardware (items) and software licenses (G/L Accounts) will be purchased from vendors like Microsoft.

The projects can be divided into large and small projects. The larger projects are new implementations and upgrades. Smaller projects are usually implementing small features and helping users with regular support issues.

Invoicing can be done in various ways. New implementations and small projects can be invoiced per billable hour while upgrades are sold at a fixed...

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