Lasernet BC Connector 4.3.3.0 New Features and Fixes

Lasernet for Dynamics 365 Business Central

Release version: 4.3.3.0

Release date: 18th March 2025

Introduction

This page describes the new features, fixes, and enhancements in Lasernet BC Connector 4.3.3.0.

The following documentation is available:

• Release notes for Lasernet BC Connector 4.3.3.0

New Features and Fixes – Lasernet BC Connector 4.3.3.0

Lasernet BC Connector 4.3.3.0 is a quality update provided through the following new features and fixes.

#457239 - An issue with missing custom fields on the Service Invoice Line of the XML output has been fixed

In previous versions, when adding fields to the Service Invoice Line (Table 5993) in the Service Invoice report (Report ID: 12060832) via Document Layout, the data was not included under the structure of the expected lines in the generated XML. This issue has now been fixed.

#449850 - A Lasernet report for BC Report 6627 (SN Label) has been added

A new Lasernet report has been created for SN Label (Report ID: 6627). This report includes the same data as the standard report, with additional fields: Item number, Item name, Serial number, Item description, and Variant description (if available). The report can now be printed directly from the designated location in Business Central.

#449849 - A Lasernet report for BC Report 99000765 (Prod. Order - Mat. Requisition) has been added

A new Lasernet report has been created for Prod. Order - Mat. Requisition (Report ID: 99000765). This report includes the same data as the standard report while optionally also ensuring that customers can add the Operations Block using Document Layout. The report layout closely follows the standard version while maintaining flexibility for customization.

#450261 - A filter option for the Project Planning Line has been added to the Project Quote report

A filter option for the Project Planning Line/Project Task No. has been added to the request page of the Project Quote report, in alignment with standard Business Central functionality. The report now includes both the Begin and End Total at the line level, ensuring the same behavior as the standard report.

Additionally, a fix has been applied to ensure the Job Task number filter is correctly applied to Job Tasks, preventing unrelated job planning lines from being displayed. Support for Document Layout has also been implemented, ensuring data added at the line level appears within the Job Planning Line node rather than the Job Task. A more refined structure for this will be introduced in a future major update with enhanced Document Layout.

#450142 - Missing line data and totals have been re-added to the Project Quote report

In previous versions, when using Project Task Type = Posting, the Laserner Project Quote report was missing line data and totals.

This issue has now been fixed, ensuring that all relevant data, including resource hours and totals, appear correctly in the report, in alignment with the standard Business Central report behavior.

#391778 - Support for Document Layout has been added to the Job Quote report

Support for Document Layout has been added to the Job Quote report, improving the management of custom fields at the line level. While this update ensures better customization, limitations have been identified in handling additional entries at the line level. Until the next major release that will include Document Layout enhancements, adding extra entries at the line level may ential some malfunctions.

This update also introduces an optimized structure, ensuring that each line generates a single output instead of multiple outputs from different planning lines with the same line number. Future updates will further refine this structure.

#449736 - Incorrect event handling has been fixed in multiple reports

In previous versions, several reports included incorrect event handling logic, causing issues when users would run the reports without using a request page. The following bugs were found and fixed:

• Prod. Order - Job Card: The code checked for events from a service order.

• Assembly Order: Event handling was missing.

• Job Quote: Attachment handling had the wrong field reference.

• Service Contract: Attachment handling had the wrong field reference.

• Service Contract Quote: Attachment handling had the wrong field reference.

#447575 - An issue with the Lasernet Document Management page not opening in BC25 Cloud has been fixed

In previous versions, the Lasernet Document Management page did not open correctly in Cloud-hosted environments running Business Central 25. However, the page continued to work in on-premises and container-based environments. This issue was caused by changes in cue group handling within Business Central, which affected the main Lasernet menu.

To resolve this, the page has been reformatted by removing the Grid property and adjusting its structure. The new design ensures that the page opens correctly in Cloud-hosted environments while maintaining full functionality.

#451064 - An issue with diacritic characters in filters causing execution errors has been fixed

In previous versions, when using specific languages, diacritic characters would be lost when passing filter values, leading to execution issues. This was caused by conflicts between server and database collations (for instance, Czech_100_CS_AS versus SQL_Latin1_General_CP1_CI_AS).

To resolve this issue, the following improvements have been implemented:

• UTF-16 encoding is now used to store and pass filter strings, ensuring characters are preserved.

• Record.GetView(false) is now used instead of the default Record.GetView(), preventing dependency on field captions and names.

• A review of other areas using streams was conducted to ensure consistent UTF-16 handling.

These changes ensure that diacritic characters are retained correctly across all affected operations.

#451677 - Incorrect logic for determining attached lines in the Service Order and Service Quote reports has been fixed

An issue was identified in the CheckLine procedure for the Service Order and Service Quote reports. When retrieving attached service lines, the Document Type filter was missing, causing incorrect handling of attached lines in the reports.

The logic has now been corrected to include the Document Type filter, ensuring that attached lines are determined accurately.