Business Central Development

Good. At this point we know everything about exception types, what they are, how to obtain them, how to compare them (at least directly). All of these have suddenly become relevant now that we have GETLASTERROROBJECT function in NAV 2015. But an old friend is still around, the GETLASTERRORCODE function, what about it?

To continue my series about exception handling in NAV, this time I’ll discuss how to gain insight into exceptions in NAV. As I mentioned already, the GETLASTERROROBJECT function gives you an instance of System.Exception, actually of a class descending from it, which allows you to get more information about the context of the error that has just happened.

Yesterday, thanks to @sforkmann and his blog at navision-blog.de , I have learned of the existence of Statical Prism . I’ve given it a try today, and I am pretty happy – that was just the tool I needed. I won’t give a complete overview of it here, I’ll just explain that it’s a tool that reads your…

In my last post I have introduced the GETLASTERROROBJECT function that returns you the instance of the System.Exception class, representing the actual exception that has happened. To properly handle exceptions in an unambiguous way, you must use the exception type, not its name, so it is important to get the actual System.Type representing the exception type.

One more great Directions EMEA event is over, and it was a great experience again. I am a bit sorry, though, that my main focus was delivering presentations, so I enjoyed myself less mingling around, meeting new folks and consuming content. But it was still a great event.

Even though my blog queue has a lot of far more interesting todo entries waiting for their prime time, on my short flight to the Directions EMEA conference in Poznań, instead of dozing away or blank-staring through the window, I’ve decided to introduce the…

Once upon a time, a smart bloke named Saikichi Toyoda came up with a 5 Whys troubleshooting technique. It postulates that you only need to ask “why” five times to get to the root cause of any problem in a cause-and-effect sequence.

Use Labels (View > Labels) instead of data columns for captions in your reports. It’s amazing how much you save in terms of data transfer. And your Data Set looks better too. Microsoft, why don’t you use this consistently on your standard reports?

Upgrade projects are lots of fun. They are full of challenges that keep you busy day and night all the time. I have encountered a very interesting challenge on my last upgrade project. The object upgrade process was completed, the data upgrade procedure ready to go, but when we started first tests we realized that the data upgrade execution takes some 39 hours to complete just Step 1.

When testing the upgrade process, it’s a good idea to make a backup after every significant step, such as after importing Step 1 upgrade objects, after completing Step 1, after converting the database, and so on. This way you can always resume from the last meaningful point and save a lot of time, as compared to always running the whole process from the beginning.