Business Central Development

Microsoft Dynamics NAV Team Blog has just published a mega-useful post about recommendations for configuring Microsoft SQL Server for optimum Microsoft Dynamics NAV Performance. If you haven’t yet, you should check it here .

We old dogs really have to learn new tricks with RTC (RoleTailored Client), as I found out couple of days ago. A customer of mine asked me for a quick report. I don’t typically do reports, but I thought— “not a big deal, it’s just a report” —so I fixed it, tested it, made sure it worked, then deployed it to production.

While designing a custom functionality for a customer, there was an issue with posting groups: the way the custom functionality was designed would result in value entries being always posted to a single posting group, resulting in inventory balances always going to the same inventory account.

Microsoft Dynamics NAV comes packed with a set of predefined roles for many tasks such as editing or posting journals, creating sales orders, editing fixed assets, etc. It also comes packed with a SUPER role, which can do just about anything it wants. There are two problems with the SUPER role.

So I would guess that was it. I’m just returning to Kristiansand, my Norwegian base, after delivering the “Microsoft Dynamics NAV 2009 Development Best Practices” course to a partner, my first custom-developed training ever. My impression is—mission accomplished. I was not sure at first how this would turn out.

“Best practices” is one of those beloved and hated concepts. There are people who just embrace “best” practices for the sake of their bestness . And there are people who just shun them for the very same reason—those know-it-alls who have opinion on everything and know it better before even learning about it.

Microsoft Dynamics NAV Classic client has some features which are simply unbeatable when it comes to productivity and speed, one of them being primary-key filtering. When you set a single-value filter on primary key fields in a table, and then insert a new record in the same table, primary key fields are automatically populated with values from the filter.

If you try exposing Page 5 Currencies as a Web service in Microsoft Dynamics NAV 2009, and then consuming this web service through a .NET application, you are almost guaranteed to encounter some unhelpful and generic XML errors that give you absolutely no clue about what exactly, where and why, went wrong.

This is bazillionth time that I’ve encountered this issue, so I’ve decided to post a solution to it. If you live in a country which doesn’t have Microsoft Dynamics NAV 2009 localized version yet, you might have tried installing the W1 (worldwide, English, non-localized) version. Did it work out?

Hint: this is a post for developers, and mostly junior developers, those who are still learning how to code properly. I know, I promised not to blog about stuff like this, but I simply couldn’t help this time. A friend of mine has asked me for help. “There is this C/AL function I had to rewrite, now I end up with 106 BEGINs, and only 105 ENDs.