Author: jr

Since version 2 of Reports ForNAV, you can have multiple versions of the product installed and in use at the same time. This means that your reports can use different versions of the ForNAV add-in. If you want to know which version you are using for a specific report, you can look in a couple

Working with printers is known to cause headaches. Both connection and performance can be difficult to get right. The mix of printers, printer ports, spooler services, print servers, security, and drivers sometimes makes it difficult to locate the problem. Here are some general hints and guide lines to help you if you experience problems: Make sure that

We have observed that the Windows feature called Data Execution Prevention (DEP) can crash programs that use Microsoft.NET components. So far, this behavior has been isolated to Windows Server 2008 R2. If you experience that using of ForNAV is crashing your server or your client on Windows Server 2008 R2, you should try turning DEP off

If you get the error message TableData 9651 does not exist when you compile a report object in NAV, you must check your NAV Compatibility option. This message means that your object was created for another version of NAV, where the table 9651 Report Layout Selection exists. In the ForNAV Designer and Converter, there is an option called

With Reports ForNAV, you can change the used report layout at runtime. This means that you can load a layout, which you have stored in a file or a blob field and use that instead of the default layout. This feature was introduced because a ForNAV customer wanted to change the invoice layout based on

When the reporting runtime creates PDF documents using the Bullzip PDF Printer, it has a timeout setting to control the process. This timeout will make sure that the NAV service tier regains control even if the process does not run as planned. Up until build 1068 this timeout had a default value of 5 minutes.

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