Category: Knowledge Base

Using the OData web service for the Fields page (7702) can sometimes be a problem because of firewalls or other network settings. Therefore, we offer the alternative solution of exporting your NAV table definitions to a text file and then using that with the Converter and Designer. The programs need access to field information, because

This article describes what to do if you experience problems with specific fonts on your system. We have seen a couple of issues where a font was expected to show in a report but for some reason it displayed garbage or random characters, or nothing at all. Here are a couple of solutions to common

In NAV, Classic bitmaps were drawn using their own resolution and anything that could not fit into the control was clipped. When using the ForNAV Converter, this means the sizing is set to “Normal” to get the same behavior. However, the default behavior of RDLC is to zoom the bitmap, and many new NAV installations,

This is a knowledgebase article on totals and what to do when variable names or field names used in totals are changed In Classic, totals were controlled by the TotalsFields/GroupTotalFields properties and the C/AL function, CREATETOTALS. However, these were removed in NAV2013 and do not exist anymore in standard NAV. Because of this, these properties

If you have the Reports ForNAV Converter or the Reports ForNAV Designer installed on your client, just open one of them and choose either Help or Settings and About:   If you are running the reports only (and do not have our tools installed on any client) – you have to go to the service

If you see an error message where the NAV server or client cannot create an instance of the object, then you may have a security problem. This problem is not the same as when it cannot load the object. When NAV loads the add-in it only needs read access to the DLL file. However, when

 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

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

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

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