It’s hardly any news for the lucky 21 countries which have had them by default for about two years, but for other 18 which haven’t, there is an alarmingly low awareness about three interesting NAV functionalities: Liquidity, Cost Accounting and Kitting.
These three have been named Local Functionality, which means they are a part of a localized version in some of the countries. For other countries, this functionality is not available by default, but it doesn’t mean it can’t be licensed or implemented for customers in other countries as well.
There are three kinds of people: those who watch things happen, those who make things happen, and those who wonder what happened.
The world is in crisis. Some countries are hit harder than the others, some markets have sunk deeper than the others, but the effects of global economic recession are obvious, and if the crisis didn’t hit you yet, fasten your seatbelt—it surely will.
With the whole world wondering what’s going on, the winners will be those who learn to navigate the troubled waters and make things happen. This is much easier with a piece of good business management software, such as Microsoft Dynamics NAV.
When you are making a decision to implement any large scale business management or ERP system, it can take dozens of presentations to learn about the functionality, and you might still have a number of questions lingering in the air unanswered. With this functionality catalog I hope to help you deciding on implementing Microsoft Dynamics NAV by explaining in detail most important application features, so you can easily get the picture of system out-of-the-box capabilities.
The first round of Microsoft Dynamics NAV Functionality Catalog has been written, giving you basic overview of application areas of Microsoft Dynamics NAV from business processes functionality perspective. It’s going to grow, so do drop by. You can visit the catalog by following this link.
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.