The NAV Developer Preview is meant to create extensions and not to do any customizations in the base application. However, you may want to have at least access to the base code to see what has been changed, which functions are external, etc.
If you created an Azure VM right away after the announcement of the September Update, you might be missing C/SIDE on the desktop. If that is the case, then you should recycle your VM and create a new one. The latest image version contains a C/SIDE shortcut on the desktop. Or you can skip to below how to get access via PowerShell.
On the desktop you will find a shortcut FinSql.
It will automatically try to open the correct database, but you have to type in credentials.
These are the credentials you muse use:
- Username: SA
- Password: same password as NAV admin user
The server name is: NAVSERVERSQLEXPRESS
With this, you should be able to connect to the database, change the license and export objects.
To access with PowerShell follow these steps. These steps also demonstrate how you can exchange files between the container and the host system.
All steps below should be executed on the Azure VM
Step 1: Copy a development license to the folder C:myfolder
This folder is shared with the docker container. Inside the docker container it is known as C:runmy.
Step 2: Open the NAV Container PowerShell prompt from the desktop
Step 3: Import the development license to the NAV server
Run this command:
Import-NAVServerLicense -ServerInstance NAV -LicenseFile 'C:runmyNAV2017 USA.flf'
Again, the folder C:myfolder on the Azure VM becomes C:runmy inside the container.
Step 4: Get NAV Server settings
Run this command:
Get-NAVServerConfiguration -ServerInstance NAV
Now you know the database details. You need them for the next step.
Step 5: Export the NAV objects to text
Run this command, and use the settings you found in the previous step:
Export-NAVApplicationObject -DatabaseServer localhostsqlexpress ` -DatabaseName FinancialsUS ` -Path C:runmyNAVTenerifeObjects.txt
And you will get the complete export in C:myfolder on the Azure VM!
Step 6: Explore it with a source code analyzer
Load the object file into a C/AL code analyzer of your choice.