Get the answer to all your FORNAV questions
Knowledge Base
-
Upgrading ForNAV Reports to NAV 2017
In NAV 2017, the layout of the Custom Report Layout table (9650) has changed, which means that if you want to upgrade your ForNAV reports to NAV 2017, you have to upgrade to ForNAV version 1.3.0.1006 or newer. If you have previously converted your reports from “classic” (that is, NAV 2009 and earlier versions) to…
-
Upgrading classic reports using COM automation or Office integration
If you have reports using COM automation or have code depending on standard NAV Office integration, such as the Excel buffer, you must upgrade your C/AL code to adopt the new interface(s). In most cases, you will get a compile error when you try to compile your converted reports – but in some cases, you…
-
Client add-in cache
Since Dynamics NAV version 2015 the server can send add-ins to the Role Tailored Client when they are needed on the client. This is a great feature, which helps add-in developers deploy the solution without much effort from the developer or the end user. However, this automatic deployment does not send updated DLL files to…
-
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…