NAV Development Preview – September Update


Welcome to the September update for the Developer Preview. In addition to the next batch of fixed issues we announce the following changes:

    • We have a new developer preview image ready for you. To get up and running, follow these steps:
      • Navigate to http://aka.ms/navdeveloperpreview to launch the September update of the Developer Preview.
      • Specify Resource group, Vm Name, and Admin Password and then select which country version you want.
      • When deployment has succeeded, you'll see following the landing page (Open the Virtual Machine DNS Name URL in a browser).

      • You can connect to the Virtual Machine using Remote Desktop and Open VS Code to develop like before.
      • Or, you can develop using VS Code on your local computer. To do this you must download the self-signed certificate and install it in the Local Machine Trusted Root Certification Authorities. Having downloaded and installed the certificate, you can download the AL Language Extension and install it into your local VS Code.
      • Use AL GO! and replace the corresponding lines in launch.json and app.json with the lines you see on the landing page. Download symbols, compile, deploy, and debug.
    • The .navx file extension for AL packages has been changed to .app
    • The developer endpoint on the Dynamics NAV server now performs license checks when publishing AL projects. Developer Preview environments offer a free demo range of 50100-50149. Dynamics 365 for Financials sandboxes have a more permissive license that lets you use range 50000-99999 as well as the 70000000-75000000 range.
    • The developer endpoint on the Dynamics NAV server now performs permission checks to see if the user who is trying to publish an AL project has the rights to do so. The indirect insert permission into the Nav App table is validated. This permission is a part of the "D365 EXTENSION MGT" permission set.
    • It is now possible to define Watches and conditional breakpoints in the new debugger. In the Activity Bar in Visual Studio Code, choose the Debugging icon to bring up the Debug view and add Watches. Use the Debug Menu to set breakpoints in the code.

Let us know how you like working with these additions and keep submitting suggestions and bugs. You can see all the filed bugs on our GitHub issues list (https://github.com/Microsoft/AL/issues). To get an updated image see the steps above for getting it or jump directly to the Azure Gallery signup at http://aka.ms/navdeveloperpreview.

For a list of our previous blog posts, see the links at the end of this post.

/NAV

Our earlier blog posts:

NAV Development Tools Preview - August Update

NAV Development Tools Preview - July Update

NAV Development Tools Preview - June Update

NAV Development Tools Preview - April Update

NAV Development Tools Preview - March Update

NAV Development Tools Preview - February Update

NAV Development Tools Preview - January Update

Announcing the Preview of Modern Development Tools for Dynamics NAV

Comments (21)

  1. Salva says:

    I just deployed the new preview image in my Azure subscription, connected to it using remote desktop, opened Visual Studio code, opened the “HelloWorld” folder example, pressed F5… and got an ugly error: “command ‘al.resolveDebugCommand’ not found”.

    Are there any extra steps that should be done after deploying the new image?

    P.S. I also downloaded the vsix extension to my local machine and get the same error when I try to create a launch.json file for Dynamics NAV.

    1. Hi Salva,
      Could you please confirm that you’re using the right AL Language extension version? You should be using 0.9.12794

      1. Also note that F5 will start the debugger. To deploy and run without debugging you should use Ctrl + F5

      2. Salva says:

        Ok, that was weird. I just started the vm again to double check the version… and the powershell that installs VSCode, the extension, and the examples, reinstalled everything again (Is it supposed to run every time I log in?)

        After starting the Docker container (thanks to Anwar below), I reviewed the connection parammeters, pressed F5 and, voilá, this time I got asked for the username and password (I deployed the W1 server) and got the Hello World example running.

        My local machine still doesn’t work, but I’m going to guess that macOS is not supported by the extension (I didn’t mention it the first time due to the fact that I was getting the same error in the Windows VM). Could you confirm that?

        1. FreddyDK says:

          No, that was a bug. A new version of the developer preview is available now. You can remove the existing VM and create a new.

    2. FreddyDK says:

      Also note, that you have to set tenant = “” – else WebClient will not be able to start currently.

  2. Anwar Shaikh says:

    Hi,
    After the preview was deployed, it worked was able to connect the NAV Webclient.
    Restarted the VM and docker container is not running, no web client. Did anyone faced this issue? Anyway out to resolve this?

    1. FreddyDK says:

      It looks like you are right that the Container doesn’t restart on server restart.
      We will fix that.
      For now, you will need to open a cmd prompt in the VM and write: docker start navserver

  3. John says:

    Downloaded and installed, but can’t authenticate to the web client or downloading symbols. Says : “The specified user name or password is not correct, or you do not have a valid user account in Dynamics 365 for Financials.”
    Not sure what credentials to use.

    1. Hi John,
      You should use username “admin” and the same password that you provided when provisioning the VM from the template

      1. Also please make sure you are using “Local Server” deployment option when prompted instead of “Cloud” and then populate the server address with the URL that you found on the landing page of your preview VM.

  4. FreddyDK says:

    A new version of the NAV Container + VM has just been uploaded, with these fixes:
    – Container restarts automatically on host restart
    – Container still works after getting new ip number
    – Classic Development Environment supported (+ desktop shortcut)
    – NavSip Cryptography driver installed (Publish-NavApp)
    – Hide source url from status log
    – Correct downdload Urls in status log
    – Status log indicates completion after VM Succeeded

    1. John says:

      Hey Freddy,
      Could you add the links to powershell for NAV Administration and Development as well?

      Thanks!

    2. John says:

      Hi Freddy,
      I’m having problems compiling from the dev environment and launching the editor from the dev client. Looks like it has issues connecting to port 7045 on the navserver.

      John

      1. The samples has not been updated with “navserver” as the service name, port 704x are open on navserver:704x not on localhost:704x..

      2. Varun says:

        Hi,

        I am also facing the same issue as John,

        Can you tell us what is the solution for this

  5. Jeroen Hems says:

    How do I connect to the database using finsql? I tried admin and the password specified at vm deployment, but that doesn’t work (login failed). I’m guessing it’s a password problem. Mine contains upper and lower case letters, and some numbers, and it’s 16 characters long.

    1. Jeroen Hems says:

      So it turned out not to be a password issue, but a non-existing SQL Login. I had to create the admin user with my password, using sqlcmd from the container command prompt, and was now able to login.

      1. Pallea says:

        Strange. I did not have that issue, here it worked “out of the box”.

        1. Jeroen Hems says:

          @Pallea, weird indeed. Which localization did you choose? We’ve chosen GB. I’m no expert in docker, but it seems to me that there may be different containers for each localization with their own SQL and NAV setups. Maybe that’s why it behaves different for you.

    2. Lars Westman says:

      User SA and the password you have setup for admin works

Skip to main content