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

Version and object management

When doing software development, discussing version management is unavoidable. Microsoft Dynamics NAV is flexible in this and allows developers to make their own decisions on this subject rather than forcing them to one way of versioning.

What is a version

In Microsoft Dynamics NAV, there are two ways of determining what a version is. The first and easiest approach is to change the version of an object each time it changes. The initial released Version is 1.00 and each change increments to 1.01, 1.02, and so on. A big change will lead to Version 2.00.

Another more common approach in Microsoft Dynamics NAV is to group version numbers in releases of a group of objects together. When this is applied, the application gets a version number that is incremented each time we release. This means that an object with version number 1.01 can jump to 1.04 if it was not changed in releases 1.02 and 1.03.

Version numbering

There are rules in Microsoft...

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