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
Implementing Microsoft Dynamics NAV - Third Edition

You're reading from   Implementing Microsoft Dynamics NAV - Third Edition Implementing Microsoft Dynamics NAV 2016

Arrow left icon
Product type Paperback
Published in Apr 2016
Publisher Packt
ISBN-13 9781784397555
Length 492 pages
Edition 3rd Edition
Arrow right icon
Author (1):
Arrow left icon
Alex Chow Alex Chow
Author Profile Icon Alex Chow
Alex Chow
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Exploring Microsoft Dynamics NAV – An Introduction 2. What's New in NAV 2016? FREE CHAPTER 3. Dynamics NAV – General Considerations 4. The Implementation Process – From the Reseller 5. The Implementation Process on the Customer Side 6. Migrating Data 7. Upgrading Microsoft Dynamics NAV 8. Development Considerations 9. Functional Changes on Existing Implementations 10. Data Analysis and Reporting 11. Debugging 12. Popular Reporting Options with Microsoft Dynamics NAV Index

No save button

Dynamics NAV does not have any kind of save button anywhere in the application. So, data is saved into the database as soon as the user leaves the field.

Likewise, a record is inserted in its table right after the field (or fields) of the primary key. Some pages such as Sales Line and the different journals have the DelayedInsert property set to Yes, which means that the record won't be inserted until the user moves the cursor to the next line or the next record.

The main advantage

The major advantage is that users can create any card (for instance, Customer Card), any document (for instance, Sales Order), or any other kind of data without knowing all the information that is needed. Let's explain this with an example.

A new customer has to be inserted into the database. For Dynamics NAV, it is mandatory to fill in some information to actually be able to post any transaction with the customer. The mandatory fields are Gen. Bus. Posting Group and Customer Posting Group...

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