Not-so-elementary costing: The Change

  • Post comments:6 Comments
  • Reading time:6 mins read

They say the only constant is change. I’d say that the only other constant is error. We humans tend to err. Give a repeatable task to a human, and they’ll mess it up every once in a while. Some call it the human factor.

One of the many repeatable tasks in Microsoft Dynamics NAV is setting up items. If you remember my rant about mandatory fields, and how I said they were baaad, there might be an even more baaad kind of fields: the default value fields. Because the system simply inserts a value into these fields without asking for your say, and if anything is easy, it’s only so easy to overlook these. Yep, you have a chance to voice your oppinion on these, but having got to hurry for a cup of coffe with Mary from accounting, admit it, you’re gonna leave that default FIFO costing method for an item every once in a while, even though it should really have been Average. Then you’ll start posting. Then your phone rings and starts screaming at you about a moron who screwed up items again.

(more…)

Continue ReadingNot-so-elementary costing: The Change

Purchasing Services: Inventory Value Zero

  • Post comments:4 Comments
  • Reading time:4 mins read

I’ve stumbled recently upon a support request, where a partner asked if there was a possibility to register purchases of services in Microsoft Dynamics NAV. When it comes to selling services, such as consulting, or repairs, NAV is your true friend, because you can use Resources to register sales against them. However, purchase documents don’t offer a possibility of purchasing resources, so you are left to some workarounds.

(more…)

Continue ReadingPurchasing Services: Inventory Value Zero

Output journal confusion

  • Post comments:4 Comments
  • Reading time:6 mins read

A few days ago, I’ve got a question from a customer, about an alleged bug in Microsoft Dynamics NAV. According to online help, when you are posting output in manufacturing module, the last line of the type Output in the journal will actually adjust the inventory level. However, what is not explained is how the figure in this field is calculated, and why exactly that way.

When you decide to post an output of a production order, you specify the released production order for which you want to post the output, then call the function Explode Routing. After this function completes its chore, users unfamiliar with how manufacturing works can get quite confused, because two of the fields the procedure fills in contain unexpected values. These two fields are Output Quantity, and Scrap Quantity.

(more…)

Continue ReadingOutput journal confusion

Scrap the crap

  • Post comments:2 Comments
  • Reading time:1 mins read

Scrap happens. So does sh*t. In my last blog post about scrap I gave a crappy explanation of how forward calculation of fixed scrap works. So instead of disgracing myself by leaving the…

Continue ReadingScrap the crap

Automated version management? Of course!

  • Post comments:16 Comments
  • Reading time:6 mins read

Imagine that whenever you edit an object in C/SIDE Object Designer, and save it, the system automatically saves it in the version history. Imagine that it never simply overwrites your previous version, but keeps all of them there for you. Imagine that you can see all of the modified versions of any object, then make any version the current version by doing as much as a single mouse-click, no tedious imports and exports needed. Imagine that this is true for all of the developers on your team. Imagine that it is completely, fully automated.

(more…)

Continue ReadingAutomated version management? Of course!