Author: Jan Sillemann

Microsoft Excel reports in the ForNAV Report Pack

The ForNAV Report Pack 7.0 contains a set of out-of-the-box Excel reports to enable exporting aggregated data from the Business Central Ledger tables.   Each report can be run from their respective parent page (Customer List, Vendor List, and so on).   On the request page, you can select the language of the Excel sheet

Continue Reading

Creating a Microsoft Excel report with ForNAV

With ForNAV 7.0, you can create a custom Excel report, which has several benefits.   You can: Create the report without writing AL code – it only requires knowledge about the Business Central data model. Easily add data from related tables. Create a separate Excel worksheet per data item, which is better suited for Excel

Continue Reading

Override printer selection with an event

In situations where the normal use of the Printer Selection page is not enough to select the right printer for the current user, there is an event to help you override the printer selection. It is a standard event that is called before the request page is shown. The following code is an example of

Continue Reading

Create an email body layout for a custom report

This article describes how to create a new email body layout for a custom report. This is only relevant in an On-Premise installation with the DLL version of ForNAV. For any Universal Code installation (cloud or On Premise), this article is not relevant because in a Universal Code installation you can use any Custom Report

Continue Reading

Add Assembly Lines to any Business Central report

With the release of ForNAV 7.0, it is now possible to add Assembly Lines (Bill of Material or BOM) to several standard ForNAV reports. Note: Adding temporary Data Items in this way only works when you create a custom report layout. If you create a new report, you must write the AL code to insert

Continue Reading

Change the folder of the extension layout files

When you create a new Business Central report in an extension, you get two files: an AL file, which contains the code, and a layout file, which contains the layout information of the report. By default, ForNAV stores all the layout files for new and converted reports in the Layouts folder of your extension. In

Continue Reading

Footers with company information

Use HTML content to create links in email bodies. This article walks you through the process of making a nice-looking report footer with some company information. Creating footers for PDF documents and email body text requires different techniques, which is also covered. This is an example of a footer text: This footer has the following

Continue Reading

Parallel print job processing

By default, the jobs in the print queue are processed in sequence. The local print service downloads one job at a time and prints it before getting the next one. If this approach is causing long waits in your way of printing, then there are a couple of things you can do. Add another print

Continue Reading

Empty custom report layout

When working with custom layouts in Business Central, you sometimes end up in a situation where the system cannot find the layout it is looking for. In cases like this, the report is run with an empty layout. Empty layouts make the report execution fail. Why is my layout empty? Empty layouts can happen for

Continue Reading

The webclient sometime hangs when creating more than one report at a time

When saving more than one RDLC or Word report within the code path of saving a ForNAV report, the client sometimes hangs. The root cause is the Business Central Reporting Service, which sometime hangs when the second report is rendered. To get around this issue, you must disable the Reporting Service in the Business Central Administration

Continue Reading