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 was never this excited about a new job, and this is my fifth new job in my career. And I never felt this much responsibility. And this much challenge.
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 enter the data of a new record, without having to press F3 (or inserting a new record manually). The problem is, this doesn’t work that way in Dynamics NAV.
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. Last time I wrote about technology and functionality I wrote a disertation. This time, I’ll be quick.
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. So far, this is the situation with my blog, and I don’t really mind if it stays that way for the time being.
Ok, I’ll get to the point. There is a change in my career path on the horizon. Nothing really radical, because I am staying in the same business, I am continuing to work with the Microsoft Dynamics NAV, but my work might be a little bit different. To be totally honest, this was on the horizon for quite a while, but there have been some, err, circumstances, and I wasn’t really sure whether it will be go, or no go. Now it is 99% go, but yet I don’t feel comfortable to blurt it out all at once. Suspense is the key…
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. Inspired by a total lack of resources which would give a clear picture of all the system components and their relationships, I wrote this post in hope someone might find it helpful.
It has been a while since I was here, and I will not try to make any excuses. I could say that I have been busy (which would be true), and that I have a family that I love spending my time with (which would also be true), but true reason is the one you all know: I have been lazy.
Last time I promised to say a word or two about convergence once. Let me do it this once.
Few days ago, when I wrote about Navision, I made an on-purpose mistake: I kept talking about, well, Navision. It’s wrong. And it’s not.
The story is not very short, but let me strip it down to the bone.
I first heared about Navision five years ago, when I was working as a .NET developer on a web shop project. One of my tasks was to integrate the ordering functionality with customer’s existing system using the fixed format document exchange. At that time my whole world was object oriented, I used C# more than any other language, human or computer, and solution to any problem started with { and ended with }. Business logic was farthest I went in touching any business problem. Business was for businessmen, I was a programmer.