This blog started enthusiastically, I had as many as 14 posts per month. Taking into account that blogging was only a hobby, I blogged like crazy. Then I went silent.
No, I wasn’t tired from blogging, I didn’t experience a writer’s block, quite the contrary! I was working on a project. A top secret one. Now it has been done, and here are the results: a book called Implementing Microsoft Dynamics NAV 2009.
You are consulting for a customer, and they ask you:
– “There is a problem with setup for this item, when I calculate the requisition plan, the system suggests purchasing it, while I have it on another location, and I’d like it to suggest transferring it from that location, instead of purchasing it. Can you fix it?”
Assume you aren’t completely sure in the answer. What do you tell them? What do you do?
The long awaited Microsoft Dynamics NAV 2009 has been released for download earlier this week, and has just been publicly announced at Convergence 2008 Copenhagen. If you have PartnerSource access, you can download Microsoft Dynamics NAV 2009 here.
This one is the most important release of Microsoft Dynamics NAV ever, as it brings a completely new architecture, a shiny new user interface, web-services enablement and much more.
Last Friday, while enjoying a not-at-all healthy Salisbury steak with cheese, I had an interesting discussion with a partner: should NAV consultancies create default databases?
A default database (in this context) is a packaged solution built upon standard Microsoft Dynamics NAV, where a consultancy has introduced a number of features that they sell to all their customers as the standard solution, instead of standard NAV. The modifications to standard NAV can range from simple report adornments to minor feature improvements to full-scale horizontal or vertical functionalities.
One of many improvements the latest version of Microsoft Dynamics Sure Step methodology has brought along is the revised purpose of the Functional Requirements Document (FRD). This document has long served as cornerstone of every Analysis process of every implementation project: it was the main deliverable of the Analysis phase and it both documented customer’s requirements and explained how they will be met with Microsoft Dynamics NAV solution.