From the Microsoft Dynamics NAV Blogs: Extensions pain; PowerShell module; Automate translation; Employee account type

In this week's Microsoft Dynamics NAV blog roundup:

• Microsoft Dynamics NAV extensions and the add-in pains
• CRS.RemoteNAVDockerHostHelper - my new PowerShell module
• How to automate translation process in NAV
• Dynamics NAV 2018 - employee account type

Microsoft Dynamics NAV extensions: Painful experiences

On the Stefano Demiliani Technical Blog, Demiliani stated that recently he had been in contact with a number of partners attempting to migrate their NAV solutions to the new Extensions V2 architecture.

However, Demiliani stated that this task is more than just a simple migration. Rather, the solution or at least some parts of it need to be re-engineered. The real problem migrating many NAV solutions to Extensions V2 and AL is one: porting custom NAV add-ins to AL.

So, the real problem that many partners actually have is essentially this: how can I do the jump to AL and Extensions V2 if my add-in (that's a core part of my solution) can't be ported to the new platform at 100% full features that we have actually and that customers needs?

According to Demiliani, at the moment, there's no clear answer to that question. In fact, users are forced to adapt it to what the AL platform actually is offering, which he doesn't believe is enough. What is needed is the full power of .NET in AL.

Demiliani stated that he has a couple ideas to share with the Microsoft team to solve the problem. You can read about them here.

CRS.RemoteNAVDockerHostHelper - my new PowerShell module

On Waldo's blog, Eric Wauters stated that he's been struggling trying ...