The debugging process is for many people one of the most tedious tasks a developer has to do.
Depending on the complexity of the process you are trying to debug, this action can take from a few seconds to a few hours. A few hours of seeing the same lines of code over and over…
If we add to that the fact that some processes are loops and the same code is repeating itself when you only need one of the iterations (the processing of the sales lines when posting the invoice for example), the end result is a very time consuming course of action to follow.
As developers we are often faced with the choice: going with your gut or doing the due diligence and completely debugging the malfunction.
Microsoft knows this and when they can, they add some goodies to help us out as well as heping customers! This is one of them Continue reading
Finally! How many hours have I spent debugging sessions without UI with MESSAGEs and ERRORs… The good old days.
If you have done that, like me, then you will probably agree that it was not the most elegant way of finding the source of the problem. Have you ever forgotten to delete a funny MESSAGE after a session debugging with that method and had the client bring it up? I know I have.
In any case, we can finally use the debugger tool incorporated in NAV to debug the sessions without UI. That’s great. And this includes ADCS sessions too!
This is something we have been able to do for a while now, but I did not want to lose the chance of writing a post about it.
How can we do this you might say?
Let’s get to it! Continue reading
Up to NAV2009 we had at our disposal the option of closing sessions from the same form we could see the sessions on. But unfortunately this option disappeared in NAV2013.
The page where we can see the same info is now the debugger, and does not have a “Kill session” option we are looking for.
What can we do in this version then?
A new function was introduced called “STOPSESSION”. It enables us to do the same thing we could do before.