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.
-
Cross reference information
To support Microsoft Dynamics NAV/Dynamics 365 Business Central cross-reference tools, such as the Advanced Object Manager and Statical Prism, you can now create cross-reference information in ForNAV for fields used in the ForNAV report layout. In the Converter, you simply select the Add cross reference information in code checkbox: This results in a new…
-
Uploading vs. changing the Microsoft Dynamics NAV / Microsoft Dynamics 365 Business Central license
The ForNAV Designer tries to get the report object source code directly from Dynamics NAV/Business Central. It uses the finsql.exe to export the object in text format. This step requires a NAV/Business Central developer license on the NAV/Business Central server. Because the finsql.exe uses the license on the server, it is not enough that you…
-
OData, Web Services, and Page 7702 not in the customer license
When running on a standard Microsoft Dynamics NAV or Microsoft Dynamics 365 Business Central license, you might have the issue that you cannot enable OData and you are not able to run the Web Service required by ForNAV, because you do not have permission to execute the page 7702 (Fields). The error message is: “Could…
-
Backslashes and line breaks
In Microsoft Dynamics 365 Business Central, a backslash sometimes represents a line break in the text. This works really well unless you actually want to display the backslash character instead of a line break! With ForNAV, you can show the backslash in a text box if the multiline property is set to no. If the…
-
Characters are shown as square boxes
Some output types, such as PDF or Microsoft Word can sometimes show characters as square boxes or not at all. The reason for this is typically that you are using a font that does not contain the characters that you are trying to display. Especially Asian languages use characters that are unknown to most Windows…
-
Troubleshooting Excel export
If you experience problems exporting your report to Excel, starting from version 4.0.0.1613, you can run ForNAV in debug mode and send the debug files to ForNAV Support for troubleshooting. To enable the debug mode: In the registry database on the service tier machine, under the registry key HKEY_LOCAL_MACHINESOFTWAREForNAVReports ForNAV, add a value named DebugMode…
-
PowerShell CmdLet2
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 |…
-
Custom Fonts
Using custom fonts in reports has always been tricky because you used to have to install the fonts on both the server and the client machines. With ForNAV, you can now use custom fonts in your reports without having to install these fonts on your service tier and client computers. The ForNAV Designer detects that…
-
Layout changes are not saved
When you save directly to the NAV database from the ForNAV Designer, you might experience that it looks like your report changes are not saved, even though no error is displayed. The most likely explanation for this behavior is that your NAV settings in the Designer are pointing to another database. Therefore, your report object…
-
Using the ForNAV Converter to convert txt to AL
The new version of the ForNAV Converter now supports conversion of any C/SIDE object to an AL extension, and you can even keep your reports in RDLC format if you are not ready to migrate to ForNAV reports yet. This means that the ForNAV Converter offers you the added value of being a free, single-step…