The other day we found out that some part of one of our extensions was not uploaded to our source code repository and no local version was available anymore. But we did have the .app file. I knew from extensions version 1.0 that the extension file, the .navx, was a zipped set of files. The x in .navx is pointing at this as with all office file extensions now a days. You might recall one of my old posts . As per this blog post, but then in reverse order, would I be able to unzip the .app file by…

[Just a note to myself as I always need to look up what to download and install on Visual Studio 2017 to allow me to work on RDLC layouts for my reports.] When opening the layout of a printable report from C/SIDE report designer Visual Studio 2017 will be opened. When you have a new installation of VS 2017, the layout will however be shown in xml format only. In previous versions of Visual Studio the issue was solved by installing SQL Data Tools Trying the same for VS 2017 will not help you…

For those of you that have been following me for a reasonable number of years: you might have stumbled across my testimonial . It clearly marked a threshold in my professional carrier, and in hindsight it was worth all the while taking it. And now I am on the verge of adding another 7 years. Next week Thursday, to be precise, when I will be down south in California, when conference season has just taken off. My conference season and a whole new training season too. May I invite me to join me in…

Or freely translated from an old Dutch saying ( Doe de deur dicht! Je bent toch niet in de kerk geboren?): Close that FastTab! Have you been born in church? ... meaning: keep the door closed, do not spoil the heat inside. And that's what this small post is about: have a better performance by collapsing the FastTabs on your pages. After our upgrade to NAV 2018 we experienced a number of performance issues. One I blogged about some months ago. Another concerned the loading time of the Item Card…

Start of this year we upgraded our NAV 2016 installation to NAV 2018 RTM. And February 26 we were live. It was a relative smooth and fast upgrade and we were quite pleased with it. We ran however into a couple of performance issues of which one them exposed itself immediately after go-live. We were pointed to it by one of our sistering team's consuming a number of NAV web services in their application. But unfortunately we couldn't get a hold on what was exactly happening, so it was lingering…