For days this issue lingered through my mind as I felt I wanted to write something about report transformation. But what exactly? And in what format? So finally today I decided to just sit down and write. Love RTC As I wrote on one of my previous blog posts I had to learn to love RTC. Both from a user and developer perspective. During a bigger part of the development cycle of NAV2009 I had been closely involved with the Form Transformation effort. I had to use it and test it and meanwhile…

Now, after my first blog post on reporting bugs, you're in the right mood to start selling your issues. But you might be in the mist on what I mean with to-the-point repro scenario . If so read on; if not ... also read on, don't be afraid to learn. To-the-point means to me that the repro scenario will lead the engineer straight forward to the bug you are reporting. No need for her to spend too much time to get it reproduced. Just remember: the faster reproduced, the faster - and often better…

You're sitting in front of your computer doing one of your daily tasks in, let's say NAV. But @*^%$#@$$!!!!, the darn system does not do what you expect it to. Just one of these days? Might be, but it seems to you the system is not just doing something different than you expected, it clearly errs. A fix is needed to enable you to finish your task. Pffff ... no time; a busy day, but no other way than to contact the help desk at your Dynamics NAV partner and tell them a fix is need right away! Unfortunately…

It must have been somewhere in 2006 that we started testing the Role Tailored Client (RTC) and I must confess it was very hard to love RTC. But they said it was going to be a great product and it was my job at MS to test. So I simply needed a way to learn to love it. " Always look at the bright side of life, pal ", I said to myself. " Look at the RTC features not available on the Classic Client. " Here is one. At that time our team was mainly relying on manual testing based on written test cases…

And that brings me to chapter 2. Maybe less exciting, but for sure even more fun than the preceding chapter if you didn't know about it yet. Saves you a lot of time. One of the things I have always liked about NAV is the open source character of it. OK, you need the right license, but as soon as you have it you can look at any part of the code. And one of the things I probably did stress most when teaching Solution Developer classes was: if possible reuse existing code. Your customer does not…

And that leads me to one of the most rewarding things in live: sharing simple solutions. Like the next one. Typically one that probably dozens, no hundreds, of NAV pro's and user know about and at the same time numerous people have never been aware of. Years ago when working as testers on the NAV localization team (GDL) at Microsoft we were discussing how we could make our live, i.e. bug reporting, easier. Especially retyping all those lengthy error messages. OK, you could make a screen shot…