Category: Knowledge Base

From version 5.2.0.1921 and later, there is support for hyperlinks in reports. This means that for text boxes and table cells, you can set a hyperlink property that will enable the recipient of the report to click the link and open the URL associated with the hyperlink. You set the hyperlink property from JavaScript in

To add new fields to existing tables and pages faster, ForNAV 5.2 now supports the creation of Table extensions and Page extensions without having to write code in Visual Studio Code. A huge part of this is being able to figure out which Table extensions, Page Extensions, and Field numbers are available – and ForNAV

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

This article is no longer relevant and has been replaced by this article: ForNAV email body layouts