Friday, January 20, 2012

ROUND Function

ROUND function in NAV, rounds the value of a numeric variable.

For Example: ROUND(1234.56789, 0.001, ‘>’) returns 1,234.568

NewNumber := ROUND(Number [, Precision] [, Direction])

You can give your own precision in this function.

For Example: ROUND(1234.56789,0.50,’=’) returns 1234.50 i.e. nearest 50

ROUND(1234.4956789,0.25,'<') returns 1,234.25

Thursday, March 3, 2011

Series of Interview Video’s

Software Advise, which is a research company on mrp software published a series of videos with the interview from Microsoft’s Director of ERP Marketing, Guy Weismantel. Click this link to view the videos.

Wednesday, February 16, 2011

How does Dynamics NAV validates the Credit Card number for Online Payments

Dynamics NAV 2009 R2 has a new feature called “Online Services” and using this functionality you can accept and process credit card payments in Microsoft Dynamics NAV.This online credit card payment feature automates authorizing credit card amounts at the time of the order and processing the actual charge when the order is shipped and invoiced.

In order to use this online payment services, you need to setup payment services, customer payment methods and credit cards for the customers. While setting up the Number field in the Credit Card page (Customer Card—>Customers—>Credit Cards), Dynamics NAV automatically validates value for the correct credit card number and gives the error message for invalid credit card numbers.


This validation is not a real credit card number validation from the service providers but uses the algorithm called “Modulus10”. This algorithm was designed to protect against accidental errors, not malicious attacks. Most credit cards and many government identification numbers use the algorithm as a simple method of distinguishing valid numbers from collections of random digits. You can find the related C/AL code in the codeunit 827 “DO Payment Card Validation” function “IsModulus10”.

Friday, December 24, 2010

Locking and Unlocking Objects– Auto-Lock on Design

In Microsoft Dynamics NAV 2009 R2, you can lock an object in Object Designer using Lock option. Along with Lock we have other options like Unlock and Force Unlock.

Along with these features you can automatically lock an object while opening the object in design mode.

This option is available in the Tools->Options->Auto-Lock on Design.


Even though you can lock objects, it is still possible for developers to have concurrency issues, as shown in the following examples.

  • A developer opens an object in the designer but does not lock it. The developer makes several changes to the object and saves the changes periodically. At the same time, a second developer locks the object, and the first developer cannot save design changes to the object. The first developer gets an error message that the object is locked by the second developer.
  • A developer locks an object. A second developer opens the locked object in read-only mode, and then the first developer unlocks the object. The second developer still cannot save design changes to the object even though the object is now unlocked because it is open in read-only mode.

System Indicator–Dynamics NAV 2009 R2

Till now all NAV users including developers or end users felt little difficult to identify the different instances of NAV. Now we have a solution called system indicator in NAV 2009 R2 release to differentiate different instances like production environment and test environment.

Once you setup the system indicator in the company information, you can see the indicator text in the top right side of each page in the Role Tailored Client…Cool…Winking smile



NOTE: Refer GetSystemIndicator function in the Codeunit 1 ApplicationManagement.

Thursday, December 16, 2010

What’s New in Microsoft Dynamics NAV 2009 R2

MSDN is updated with the latest help related to NAV 2009 R2 Application updates and Developer updates.

Please click the link and get updated with the latest stuff.