Category Archives: Dynamics 365

Keeping track of the Microsoft Dynamics 365 Names and Products

I’m having a hard time keeping up with what names the different Dynamics 365 offerings have, and what products they come from. Maybe others are having the same issue, so here is my table:

Dynamics 365 NameOrigin Product
Dynamics 365 SalesDynamics CRM
Dynamics 365 Customer ServiceDynamics CRM
Dynamics 365 OperationsDynamics AX (7)
Dynamics 365 FinancialsDynamics NAV
Dynamics 365 Field ServiceDynamics CRM
Dynamics 365 Project Service AutomationDynamics CRM
Dynamics 365 MarketingAdobe Marketing Cloud
Dynamics 365 Customer InsightWill be part of "sales"

As you can see, there is still a couple I’m not sure of. Regarding pricing, you buy in bundles, so “Dynamics 365 Plan 1” includes:

  • Dynamics 365 for Sales
  • Dynamics 365 for Customer Service
  • Dynamics 365 for Field Service
  • Dynamics 365 for Project Service Automation

Dynamics 365 Plan 2” includes everything in Plan 1 plus:

  • Dynamics 365 Operations (AX)

Here is an odd thing, “Plan 1” costs $112 pr. user/month and “Plan 2” costs $210 pr. user/month, “Operations” alone cost $190, ie. the double of the $95 added to plan 1?

Business Edition” covers Dynamics 365 Financials (aka. NAV) but does not give you the opportunity to combine with the other 365 offerings currently. (Info taken from

Currently no pricing info on the rest, just a “Contact Us” form.

Please reach out to me at @eHougaard if I’m missing something orย  misunderstanding something ๐Ÿ™‚


Get the Modern Development Experience in Sublime Text

(Disclaimer, everything in this post is a hack, at this point, it’s all about making it work, then we can use nice folder names etc. later, read the name of my website ๐Ÿ™‚ )

So Visual Studio Code is great, and an awesome tool, but for some deep primal reasons, the choice of text editors has always been very personal for developers. My personal choice is SublimeText.

So why not try to get the new developer tool to run with Sublime?

First, let’s look at what we get in VS Code right now with the “AL Extension”:

  • Source highlighting
  • Intellisense
  • Compiler
  • Deploy

Let’s start with source highlighting

Source highlighting is the process that renders your code in specific colors based on text types and word. It looks like this in VS Code


VS Code uses TextMate format to describe the text. TextMate has become the defacto standard for syntax highlighting andย  (big surprise) Sublime Text also uses TextMate.

So the following copy command: (executed from the \users\you folder, and replace xxxx with the version number of your AL dev extension).

xcopy .vscode\extensions\\syntaxes\*.* AppData\Roaming\Sublime Text 3\Packages\User\AL\*.*

That will copy the AL Code syntax into Sublime Text’s setup. After that, when you open an .AL file, you’ll get this:


Notice that even though the colors are not the same, the coloring scheme is the same. Keywords are colored, numbers are colored, the text string in the message command is colored.

That was easy ๐Ÿ™‚

Let’s compile from Sublime Text

Next on the list is the compiler, let’s see if we can get Sublime Text to compile for us. But wait, first, let’s locate the compiler.

The compiler is called ALC.EXE and is located in the bin folder of the VS Code AL Extension (Under C:\Users\you\.vscode\extensions\)

You can supply the following parameters to ALC:

-project:<root path of source tree> (This is where app.json is located)
-out:<name of navx file>

So to build an extension, you call

ALC -project:<folder> -out:module.navx

And if everything compiles, you got a NAVX file, ready for deploy.

In Sublime Text go to Tools->Build System->New Build System…


And let’s just create one simple command: (again replace xxx with the correct version):

ย ย  ย "shell_cmd": "C:\\Users\\vmadmin\\.vscode\\extensions\\\\bin\\alc.exe -project:$file_path -out:extension.navx"

Save the file as “AL” something, navigate to one of your AL files, and press F7 (Build in Sublime Text)


Success, the AL Compiler is called from Sublime Text and an extension is created (screenshot is from a test where I checked how errors were presented).

Next chapter, deployment ๐Ÿ™‚