In this blogpost I document how to interface between extensions with workflows. I created an Azure Function and use a workflow response to call that Azure Function
Interface extensions with workflows
Tag: DYNNAV2018
Slaying the behemoth, Extension Design Principles
Fifteen minutes reading time. Once upon a time my ancestors roamed the icy plains of Northern Europe. They hunted behemoths, a single mammoth that could feed and clothe a tribe for a long while. But even though there was a lot of food on a single mammoth it was a bit of a pain to…
Symbols of madness
As you know we have been happily developing extensions for a while now. Every once in a while I blog about some stuff I found out recently but it is mostly smooth sailing at the moment. Today I was stumped though. For some reason my symbols were not loading. I make it a point to…
Dimensions of woe
So today I wanted to create a simple text variable with 3 dimensions in my extension. Normally no big deal but how on earth do I define dimensions in my variables? It turns out they are now called Arrays. So that is an improvement but the documentation is worthless. And again, nothing to be found…
Get server and database information in AL
Today I wanted to get some basic information about my NAV2018 service and database name in my extension. A quick Google found a lot of useful stuff about this but nothing that was easy enough for me. I really did not want to go messing about with xml or dotNET. This is basic stuff right?…
