JavaScript

One of major limitations of control add-ins is not being able to define HTML. It seems so unbelievably unbelievable, that anyone looking at it from the outside of the NAV/BC playground may say “obviously, you must be missing something!”. But I am not.

As a part of preparation for my last event of this year that concludes the conference season 2017 for me, I played around with the latest addition to the AL language stack for VS Code: control add-ins. If you haven’t already tried it out, or heard about it, then you should get yourself a copy of…

One elegant way of replacing your .NET interoperability code with something else is by using Azure Functions. Sounds good in theory, but what does it take in practice? And what are Azure Functions, anyway? Let me not take too much latitude, and let me just say that Azure Functions are a way of…

This year my work got a better of me. For five years in a row I have posted all my demos and materials from NAV TechDays sessions right after them. However, this year, I failed. And I apologize for this. But, as the saying goes, good things come to those who wait, and here it is – all the materials from my “JavaScript Architecture: Turning Pain into Gain” session are here.

If part of your daily job includes creating control add-ins for Microsoft Dynamics NAV, then you know that creating control add-ins that target all clients requires quite a lot manual work. There are a lot of small steps that you must do every time.

Well, control add-ins are not new in NAV 2016, they have been around for a long time now. But, they have been improved and this blog post is about these improvements. Of course, the improvements are exclusively in the Web client framework, not the Windows client, and I am educated-guessing here…

For me, Mannheim was always a yet another German city, one that beyond its name I knew nothing else about. When it was announced that Directions EMEA 2015 would be in Mannheim, my first reaction was “say what?” And yet, just as last year in Poznan, I was pleasantly surprised, and realized that every place has something to show, spirit to share, and energy to bring.

Not that I am saying it’s a good thing, but trial and error is a fairly common approach to debugging in the NAV world. We’ve all done it. Heck, even with the comprehensive testability framework built in, we all still do it more often than we’re happy to admit while sober.

In most of my JavaScript client extensibility demos, I develop the whole content of my resource ZIP files inside Visual Studio. When I press F6, magically my NAV gets updated with the latest version of JavaScript that I just wrote. So, how do I do that? Here’s the cookbook.

On Monday, June 15th I have delivered another session in Microsoft’s Road to Repeatability series of online demos about technical NAV features, this time covering Client Extensibility. The session went through both the .NET and JavaScript aspects of client extensibility, and again – I promised to post all of the demos and content from the session on my blog.