Learning about using “Reason Code” in Dynamics NAV 2009

As Dynamics NAV 2009 has been around for some time already, I thought it would be nice to refresh some of the certifications I’ve got for Dynamics NAV (version 4 is getting out of date a little bit, isn’t it)? Therefore, I started reading through “Finance in Microsoft Dynamics NAV 2009” training materials and to make things more interesting, I was trying to give myself a few questions after every chapter I’ve read.

And the funny thing is that (that’s why asking questions makes things more interesting), I had to stop at the first chapter where I have read about reason codes. At first, simple explanation “Reason codes are used to indicate why an entry was created. For example, if items from a sale must be returned, a reason code is set up to mark the reason, such as damaged, wrong color, or wrong size.” seems reasonable enough. However, if you ask yourself (or if you imagine, your client asking you) more meaningful questions: where do you enter it, how do you do that, where does it get posted, how do we analyze posted reason codes, etc, etc, you need to start digging deeper. Training course materials would not be able to answer all of these questions… Of course, you could you ask your instructor if you were on a instructor led course, but what if you are just skimming through training materials yourself?

Obviously, first thing that springs to mind – let’s google it, let’s go through mibuso, dynamicsuser, blog posts, etc. In 5 minutes I was not able to find an answer that would satisfy my curiosity, therefore I decided to have a look at Dynamics NAV source code myself.

However, I did not have a developer toolkit installed on my laptop and did not plan to do it in the next few minutes, I needed a faster solution. Which I found (remember, I mentioned googling around, skimming through mibuso and dynamicsuser forums, and recent blog posts?) thanks to a blog post: “Where Used” as simple as you can get it.

So… I have quickly downloaded Dynamics NAV W1 5.0 upgrade toolkit. Exported all CRONUS UK objects to txt file. Typed in command line findfunc “Reason Code” CRONUSUK.txt ReasonCode.txt and in few seconds I had a better understanding of reason codes than I could have had on a instructor led course. It is so much better to find an answer yourself. It might take a longer time… but you are not giving a fish for yourself, you are teaching yourself how to fish.

Technorati Tags: , , ,

This entry was posted in Dynamics NAV / Navision and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *