Category: Knowledge Base

In Microsoft Word, doing anything other than simple totaling – such as adding fields, data items or data from related tables – requires considerable development work, for example, you have to have different columns for different formatting because using Word in Business Central does not allow for macros or scripting. Maybe you’ve found it impossible

When developing on Business Central, you might assume that your data and extensions are safe from being deleted, and it is very easy to forget to take backups, especially on sandboxes where there is no customer critical data.   However, your extensions or customer layouts can easily be deleted by mistake or automatically, for example:

This Knowledge Base article is relevant for ForNAV Designer version 5.5 and higher.   Until now, it has required some coding in JavaScript to format pairs of captions/values and to hide the caption if the value is blank.   For example, in the ForNAV report pack, the standard footer looked like the following: [ CompanyInformation.PhoneNo 

We have extended the JavaScript Record functionality so that most database operations can be done without writing JavaScript code.   To change or add a JavaScript Record in a report, in the Property Grid, in the Records row, click the assist edit button (…).   In the Collection Editor, you can now add or change

JavaScript does not have a built-in function to calculate the ISO week number from a day. Therefore, to get the week number, in the ForNAV Designer, you must paste the following code into the OnPreReport trigger:   Date.prototype.getWeek = function() {   var date = new Date(this.getTime());   date.setHours(0, 0, 0, 0);   // Thursday

This article is relevant for updates up to and including BC21. For version BC22 and later, you need to upgrade to ForNAV Universal Code version For upgrade to ForNAV Universal Code version, please read this article: Upgrade ForNAV OnPrem from DLL to Universal Code —– Updating ForNAV in on-premise (OnPrem) situations is a five-step process:

Moving your ForNAV reports from on premise (OnPrem) (C/Side or extensions) to cloud is a matter of conversion. On premise ForNAV reports use a dll to render; cloud ForNAV reports use a web service, therefore you must convert your reports. This conversion is a three-step process: Upgrade to the latest version of the ForNAV Designer

With version 5.4, you can now do everything in JavaScript that you can do in AL, and much more. And the Field List in the Designer now makes it easier to use properties and functions on the report and dataitem object.   For example: CurrReport.<dataitemid>.Pdf.Append(<Rec.BlobField>) –  appends a PDF from a blob field to the

This article applies to on-premise Microsoft Dynamics NAV/Microsoft Dynamics 365 Business Central installations running the role tailored client. The Design option is shown on the request page of ForNAV reports, if the ForNAV Designer is installed on the client machine and you are a SUPER user in Business Central. This makes it relatively easy to

If you are running a ForNAV report based on version 5.3 or earlier in Business Central 16 or newer, you might run into the following error when you save your report as an Excel document: A transaction must be started before changes can be made to the database. Microsoft Excel export problems are typically caused