I’ve just got a call for help from a partner, about their customer who has decided to move from basic inventory management to full-scale warehouse management system. The question was how to post the opening balances for existing inventory quantities in flat locations to warehouse-managed ones.
I thought this might deserve a quick blog post, you can never know when someone else would want to do the same thing.
A blog reader has asked me for help about an allegedly strange behavior of items with serial number tracking. They had a customer who had serial number tracking switched on for an item with FIFO costing method. Whenever they posted a sales transaction, they chose the serial number manually. Then they noticed a puzzling behavior.
No matter the specification of the serial number on the sales lines, Microsoft Dynamics NAV seemed to be closing the item entries according to FIFO method. This effectively allowed a serial number to be sold twice (or more). They called for help.
I hate it when I don't have time to blog. I'd like if I could tell you what I've been doing, but let's leave it at this: I am enjoying…
[I edited this post once again. I see that it produces a lot of confusion, because people seem to think that this is what I claim, while I tried to convey that this is what some claim, but I think is false. Therefore, I strike this altogether, and redirect you to my original column at MSDynamicsWorld.com. Please, read that, not this. Thanks, and sorry for this mess.]
[I decided to edit this post and exclude all the argumentation it originally contained. There is no need for me to argue the same topics twice, and I really recommend that you visit and read my original column at MSDynamicsWorld.com]
(more…)
Microsoft Dynamics NAV is soon to grow a generation older, when version 2009 is finally released. I already wrote about this version, and how it will come with all-new user interface, referred to as RoleTailored client. The best way to describe the changes in the interface in everyday terms, is that it is going through liposuction. The fat client we were so used to use is getting thinner. Not as thin as it gets, certainly not anorexic, but thin enough to introduce certain significant changes.
The biggest change is that, for the first time ever, the new client is not going to be an exclusive Microsoft Dynamics NAV client. The customers will be able to use the client both as a C/SIDE (good old fat) client, and new RoleTailored client. The and in the previous sentence is not really an and, and there is a big opportunity to really misunderstand the plans and strategy, and a huge opportunity (or better threat) to totally mess up the system during a 2009 roll-out. Let me explain.