Blog

Code is boring. It is geeky. And it’s ugly, too. In C/AL it is especially ugly. While contemporary development tools come with all sort of gizmos which make coding easier, such as color-coding, auto-completion, refactoring, etc., C/AL editor seems like having awaken from a thousand-year sleep.

Today I got a comment from another soul out there, spending their time blogging about Microsoft Dynamics NAV. I’ve immediately put the link to my blogroll, and it really deserves it, because it is the best blog on the topic I’ve seen so far.

There is only one way to abort a user action in Microsoft Dynamics NAV: by using the ERROR function. This function essentially stops the execution of all code, and prevents completion of the user action, whatever such action might be. One of typical situations where ERROR is used to prevent user action is during validation of a new value in a field.

When Navision Attain attained it’s new name, Microsoft Business Solutions-Navision (the one before the current one), many other things changed as well. Good ol’ main menu was gone. Forever. Main menu was a mighty beast, one of the stronger points of Navision’s user interface at the time.

Whoa, this has been a looooong pause. If you come across some presentation, rhetoric or speach theory, most of them agree on an idea that it’s not the words that make a speach a of art, but the pauses. If the same applies to blogging, I must be quite an artist.

Technically it was yesterday, September 1st, but in practice it will be tomorrow, September 3rd, because it is a Monday. Tomorrow I start at my new position at a new company. The position is Consultant, and company is Microsoft. Quite a change for me. This change was pending for a while, and tomorrow it comes to completion.

I love unsolvable problems. I simply do. I had one a few days ago in the office, and I solved it. So, the problem went like this. A discussion has been raised among developers about whether it would be possible to display a blank form over a populated table, where user would be able to immediately…

I started this blog too seriously. Instead of starting relaxed, I jumped right into the battle head first, with difficult topics such as convergence and history of Dynamics. When I was thinking about starting this blog, one of the ideas was to discuss mainly technology and functionality.

Hello there! I could as well start with “Hello there, myself!”, but that’s a charm of blogging – you do it regardless of whether there is anyone else reading this stuff. I’ve read somewhere that most blogs have exactly one regular reader – the blogger himself.

Tons of documents exist about Microsoft Dynamics NAV, but most of them start with marketing lingo, and don’t wander away too much from it altogether. While it is nice to know that it is a system which will give you freedom to focus on your business, it is also nice to know what is it made of, and how it works inside.