Fortunately for all Dynamics NAV pro’s, some years ago, PACKT Publishing stepped into the hole in NAV documentation that had been there for years. With their last book, written by my fellow country man Mark Brummel, another and persistent gap was filled: the one left between Implementing and Programming Microsoft Dynamics NAV 2009. On this Mark has done a tremendous job “to cramp so much information in so little space “, as kriki states it.
With this review, however, I have not set out to give a complete review on all topics covered by the book, but simply want to highlight those that struck my eye.
Clearly Mark’s adage “Look, Learn, Love” applies to his book too. It undoubtedly adds a new perspective to NAV documentation which, even for celebrated NAV pros, present enough facts to make the book worthwhile reading. Mark’s long running history with NAV is guarantee to that, even though, I have to confess, I had to get used to his English phrasing. But it surely did not stop me from reading!
One of the things for which I will be frequently referring to this book in the future are the schemas. It has been a public secret for ages that one of NAV’s major flaws in (technical) NAV documentation was the schematic representation of the various functional areas in NAV, i.e. the (almost) total absence of it. On this subject alone the books has filled a major gap.
The numerous meaningful and very useful (code) examples should also be mentioned; to be learned from by any newbie developer, to be used by experienced ones.
One of the few off-topics, and I honestly hadn’t expect anything about it, nevertheless is “Testing”. As Mark himself writes (p 443) “Testing is probably one of the most important but under-rated tasks of application design”. But then only spends less than a page on it. Another gap to be filled by PACKT?
Altogether BAD is great, [Y]