You can use Reports ForNAV with your Docker containers. This is a short step-by-step example of how to set up a container that supports ForNAV reports.
Install NAV Container Helper
To help install your container, you should install the NAV Container Helper PowerShell module.
install-module navcontainerhelper -force
get-command -Module navcontainerhelper
Write-NavContainerHelperWelcomeText
Create Container
Now you can create the container with the New.NavContainer command.
New-NavContainer -accept_eula -containerName “bc150” -auth NavUserPassword -imageName “mcr.microsoft.com/businesscentral/onprem” -useSSL -updateHosts -licenseFile “C:\temp\license.flf”
Add Fonts to the Container
If you don’t add fonts to your container, it will only be able to use the Courier font in reports. Therefore, you should add some of your local fonts to the container.
Add the Arial font:
Add-FontsToBCContainer -containerName bc150 -path c:\windows\fonts\arial*.ttf
Or add all fonts from your local machine:
Add-FontsToBCContainer -containerName bc150 -path c:\windows\fonts\*.ttf
Install Certificate
Download the self-signed certificate from the certificate URL shown when the container is created. The URL in this example is http://bc150:8080/certificate.cer
The downloaded certificate must be installed under Trusted Root Certification Authorities. For more information on this please see https://www.fornav.com/knowledge-base/trusted-certificates/
Install the ForNAV Runtime
This step is optional. Starting with ForNAV 5.0.0.1805, the Designer will upload and install the ForNAV runtime DLL on the on-premise service tier if it is not there already. It will install it in the temporary files folder belonging to the service tier.
In a production environment, you should still copy the runtime DLL to the add-ins folder under the service tier. Otherwise, you may risk that it is deleted if the temporary files are deleted.
Copying the runtime DLL to the service tier is relatively easy. Here is an example.
docker stop bc150
docker cp “C:\Program Files\Reports ForNAV\Add-ins\ReportsForNAV\ForNav.Reports.5.0.0.1805.dll” “bc150:\program files\microsoft dynamics nav\150\service\add-ins\ReportsForNAV_5_0_0_1805\ForNav.Reports.5.0.0.1805.dll”
docker start bc150
Configure the ForNAV Designer
You can now connect to your Docker container from the ForNAV Designer.
Enter values that point to your docker and click test. Now you can start designing reports.
The post ForNAV and Docker Containers appeared first on ForNAV.