Category: Knowledge Base

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

Sometimes it is nice to have some kind of visualization tied to a list report. ForNAV provides two controls to enable this: Sparkline and Chart. For example: Data Table To get started, you need to define a Data Table, which can be found in the Property Grid for each data item. In the Data Table

This document describes the new features in Reports ForNAV 2.0 Installation: Side-by-side installation enables you to run reports on different versions of ForNAV (the new ForNAV Designer and Converter supports conversion to previous versions of ForNAV, if they are installed). You can choose to upgrade only specific reports to a newer version. Note This means

This article explains how NAV works with the ForNAV add-in. With version 2.0 of ForNAV, we have changed the way that we version the add-in and this affects how NAV loads, deploys, and caches it. The DLL File A NAV add-in can consist of multiple files. In our case, we have built everything into a

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

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