FORNAV
Knowledge Base
Knowledge base articles (or “KB articles”) are your go-to resource for detailed feature insights and practical tips on using FORNAV. They’re filled with essential knowledge to address almost any question you might have.
-
License Validation (old)
You may find yourself in a situation where you have a ForNAV license installed but you continue to see the Trial message on your reports. There are a couple of things you can do to check the validity of your license. Blue Trial Message If the trial message is blue then it is a compatibility…
-
PowerShell CmdLet Old
In case you want to automate the conversion of Classic or RDLC reports or reconversion of ForNav reports you might want to use the ForNav Powershell commandlet “Invoke-ReportsForNavConvert”, which has the same capabilities as the ForNav converter – but without the user interface Instead input is given as parameters: Parameter Description Default TableDefinitions <path |…
-
Reconverting reports in ForNAV
With some new versions of ForNAV, it is either required or recommended that you reconvert your reports. This is a very simple process that only takes a few minutes. You export all ForNAV reports from Microsoft Dynamics NAV 2016 (or 2013/2015) in a txt-file. To help you select the ForNAV reports, you can apply a…
-
No printer installed
If you get a message telling you that no printers are installed, then it is most likely a permission issue. When you preview reports or save them as PDF the reports are run on the service tier. The service tier is configured to run in a specific user context. If this user does not have…
-
DLL Version Problems
Reports ForNAV uses the add-in feature on Microsoft Dynamics NAV. This feature enables you to add functionality to your NAV installation via DLL files. The add-in feature in NAV supports DLL files on both the client and the server. Since NAV 2015 the server can automatically send required DLL files from the server to the…
-
A call to ForNav.Report.MethodName failed
After upgrading the ForNAV DLL, you may run into an error message similar to this one: A call to ForNav.Report.[method name] failed with this message: The type of one or more arguments does not match the method’s parameter type. The best way to resolve this type of error is to follow the steps described in…
-
Saving reports in the designer
The designer has three different ways of saving your layout changes. Save Custom Layout in NAV You can use this option if you launched the designer when running a custom layout. This will only save the layout to the NAV database for the current report. None of the dataitems or the report code will be…
-
License installation
A ForNAV license comes in the form of an MSI package. This package is digitally signed by ForNAV. The license is installed on the NAV service tier. You install it just like any other program. When the MSI package is run, the Windows Installer will add the license to the computer’s registry. This is where…
-
Troubleshooting Excel Export (before version 4.0.0.1613)
If you are on version 4.0.0.1613 or newer, you should look here: Troubleshooting Excel export This article outlines what you can do to collect information about debugging. When you get an error during export to Excel, you can collect a temporary file that will help our developers determine the reason behind the error. The temporary…
-
Image controls
The image controls in reports have a reference to an image file. In classic the reports are processed on the client computer and therefore the file path must point to a file on the local computer. With ForNAV the report is run on the server. This change means that the image file must be on…