Category: Knowledge Base

This Knowledge Base article is relevant for ForNAV version 5.1.0.1850 and higher. When using JavaScript in the ForNAV Designer, it is sometimes necessary to write conditions based on the value of option fields in Business Central/Dynamics NAV. Because of this, in the Field List in the ForNAV Designer, we have introduced a new set of

This Knowledge Base article is relevant for ForNAV version 5.1.0.1850 and higher. Sometimes, you might want to change the captions shown in reports to fulfill special customer demands or adhere to industry specific terms (for example, client instead of customer). In C/SIDE, you could do this easily by changing CaptionML strings as needed. However, in

This Knowledge Base article is relevant for ForNAV version 5.1.0.1850 and higher. Currently, the only way to add data items to a report in Microsoft Dynamics 365 Business Central is to make a copy of the report and add new data items using Visual Studio Code or in the ForNAV Designer if it is a

Setting forecolor, back color, font, and formatting dynamically on a control ForNAV supports a wide array of properties to control the look of controls. However, sometimes you might want to control the look dynamically, based on values in the data set. To do this, you use the OnPrint JavaScript trigger. The OnPrint trigger has a

You might get the following error message when printing or sending a ForNAV report: The SourceExpr for report control ‘ReportForNav_Header’ is not valid. The following error occurred: A call to System.IO.Compression.ZipArchive failed with this message: The value of Seek/OffsetFromEnd parameter is outside of the permitted range. The current value is: -18. The permitted range is:

To use ForNAV and work with the ForNAV Designer using extensions in Microsoft Dynamics 365 Business Central v14 and later, in an OnPrem (or private cloud) scenario, you must have the ForNAV granule (6188500 Reports ForNAV) configured in your Business Central license file. This is due to how Microsoft licensing and permissions work. A Microsoft

When converting RDLC reports to ForNAV reports, you will notice that the Showoutput value on sections and controls sometimes has a function call to the NavHelperFunction, like in the following example from the RDLC Purchase Invoice:   NavHelperFunction.IIFNOT(DynamicsNavDataSet.ShowInternalInfo==true && DynamicsNavDataSet.DimText_DimensionLoop1!=””,false,true)   The NavHelperFunction has been put in place to emulate some of the built-in RDLC

When your document reports are in ForNAV, you can still take advantage of the standard feature in Microsoft Dynamics NAV and Microsoft Dynamics 365 Business Central for adding an e-mail body when using the Send…, E-mail…, or Post and Send… options. For example, to use e-mail body with a ForNAV report for the Sales document

You can use Reports ForNAV with your Docker containers. The following is a step-by-step example of how to set up a container that supports ForNAV reports. Install the BC Container Helper To help install your container, you must install the BC Container Helper PowerShell module. install-module bccontainerhelper -force get-command -Module bccontainerhelper Write-BCContainerHelperWelcomeText Create the container

To import a custom report layout in ForNAV Cloud: In Microsoft Dynamics 365 Business Central, go to the Custom Report Layouts window. Click New. In the Edit window, enter the report ID and select Insert Word Layout. In the Report Name field, rename the custom report layout to something recognizable, for example, ForNAV BC custom