Showing posts with label microsoft dynamics nav. Show all posts
Showing posts with label microsoft dynamics nav. Show all posts

Programming Microsoft Dynamics NAV Review

Programming Microsoft Dynamics NAV
Average Reviews:

(More customer reviews)
Are you looking to buy Programming Microsoft Dynamics NAV? Here is the right place to find the great deals. we can offer discounts of up to 90% on Programming Microsoft Dynamics NAV. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Programming Microsoft Dynamics NAV ReviewThis book is aimed at people with some programming and business background, who plan to find their way into a NAV System. This is a challenging task, because NAV works somewhat differently to other ERP-Systems, and the author has done a good job in easing the way into a very complex application.
A simple sample application for a fictitious company is developed throughout the book. All objects ( Tables, Forms, Reports, Dataports, XMLPorts, Codeunits, MenuSuites) are first explained in their basic functions and properties, and later in more detail to implement the more advanced functions for the addon. A few of the major management codeunits which offer callable functions which every developer will look for sooner or later are covered, and by studying the way these codeunits are used the NAV newcomer will soon be able to write his own functions and subsequently his own enhancements.
Yet no one should be led to believe that after reading this book you can be let loose on any NAV System to do whatever you like. It takes a considerable amount of time to learn to estimate what impacts your coding will have in the long run, and even after several years there is always something new to learn, to fix or to optimize practically every day in an application that is making rapid strides forward. This applies even more so if you plan to work on many different databases which may have been extensively customized. But if you work your way through this book, and also take a good and hard look at the recommended internal documentations and white papers available, you will get a rough idea of what is lying ahead of you.
Of course there are quite a number of advanced topics on which you will find only a brief introduction in this book, such as the possibilities of interactions with external programs, the use of the NAV application server or automation objects (e.g. exporting/importing data to/from Excel).

A very useful comparison of the differences between the native server and SQL Server is also included. Locking, Deadlock and SQL Performance issues are discussed to some extent, but not to a degree that code examples of "do's and don'ts" are included.
There are some minor issues which I have found:
Page 246 : Although temporary tables run on the clients RAM only, all record variables in this table which are not temporary can insert, modify or delete data in the database. A seemingly harmless validate in a field trigger can lead to unexpected sideeffects. This is not mentioned.
Page 142/152 : The form triggers and form control triggers are listed ,and the author states that it should be avoided to write code in these triggers. Although this is basically true, the newcomer will find lots of code in standard forms, and will have a hard time in understanding the form and table interactions at first. Every card form needs a code line to remove the filter on the primary key, otherwise the user cannot move to the next record when the card form is called from a list form. This is not explained. Rather than removing code unnecessarily, this should be modified, as the new page object which will be introduced with NAV 2009 will have mostly an equivalent to the old form triggers as well, so it is advisable to only call functions in codeunits to avoid maintaining two similar functions in two objects.
Page 237 : It is not mentioned that a customer without the application designer granule, which small-size companies usually do not purchase, cannot import objects in .txt format. It is stated that only experienced developers should use the 2 merge options when importing .fob objects. In my opinion, this should be avoided at all costs unless any fields in the standard range have to be added which can't be created with a normal developers license when the object is of the .txt type. Then you have no choice and should perform a manual merge of the code afterwards to ensure that the code lines have not been messed up.
Page 121 : The examples for date and boolean for the AND operator are repetitions of the Not Equal operator examples.
Page 301 : Some examples of the FORMAT function would be useful. If you look for this in the index, you will find it under D (data conversion functions), not under F.
Page 345 : It is stated that Codeunits 80/90 post journal data into a ledger, but these Codeunits post Documents by transferring the data to journals, which are then posted by Codeunit 12 (G/L Ledger)/22 ( Item Ledger) etc.
Page 439 : It is stated that an executable upgrade is a one-way process. Actually, there is a backdoor if it fails, you can create an empty database with the old client, and then restore a .fbk backup which was created before installing the new executeables. A full upgrade, on the other hand, really is a one-way process.
Programming Microsoft Dynamics NAV OverviewCreated especially for experienced programmers with no previous knowledge of NAV development, this book is for people who want to learn as quickly as possible to create, modify or maintain NAV applications. The business applications software designer/developer who: Wants to become productive in NAV C/SIDE - C/AL development as quickly as possible. Understands business applications and the associated software. Has significant programming experience. Has access to NAV including at least the Designer granules, preferably a full development license and a standard Cronus demo database. Is willing to do the exercises to get hands-on experience. The Reseller manager or executive who wants a concise, in depth view of NAV's development environment and tool set. The technically knowledgeable manager or executive of a firm using NAV that is about to embark on a significant NAV enhancement project. The technically knowledgeable manager or executive of a firm considering purchase of NAV as a highly customizable business applications platform.

Want to learn more information about Programming Microsoft Dynamics NAV?

>> Click Here to See All Customer Reviews & Ratings Now
Read More...