Hint: this is a post for developers, and mostly junior developers, those who are still learning how to code properly. I know, I promised not to blog about stuff like this, but I simply couldn’t help this time.
A friend of mine has asked me for help.
“There is this C/AL function I had to rewrite, now I end up with 106 BEGINs, and only 105 ENDs. Do you have any idea how to find where this missing END belongs?”
[Updated]
I had to update this post a little bit, see below for the details, but the killer feature had to go 🙁
[/Updated]
Remeber that tool “Automated Version Management” that I published here and on Mibuso five months ago? It has just got an update: version 2.0.
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…