Lasernet BC Connector 4.4.0.5 New Features and Fixes

Lasernet for Dynamics 365 Business Central

Release version: 4.4.0.5

Release date: 23rd March 2026

Introduction

This page describes the bug fixes and enhancements in Lasernet BC Connector 4.4.0.5.

The following documentation is available:

• Release notes for Lasernet BC Connector 4.4.0.5

Note

The Lasernet Connectors for Microsoft Dynamics 365 are currently not compatible with Lasernet Core 11.0. We are working towards launching these two products together, but until then, current customers and partners with the Dynamics 365 connectors should continue to use Lasernet Core 10.

Bug Fixes and Enhancements – Lasernet BC Connector 4.4.0.5

Lasernet BC Connector 4.4.0.5 is a patch release provided through the following bug fixes and enhancements.

#500166 – The Print Log usage has been fixed to omit unnecessary commits (for developers)

In previous versions, using certain print scenarios triggered an error message stating that the RunModal() method was not allowed within an active transaction.

This occurred when calling print functionality programmatically, where a temporary Print Request Log unintentionally created a record in the system due to how request data was handled internally.

This has been fixed. The print logging process has been adjusted to prevent unintended database activity, ensuring that print operations no longer trigger transaction-related errors when Print Log is disabled and RunModal() is used.

#500517 – Custom fields added in Document Layout do not correctly apply translations to their captions

In previous versions, custom fields added to Document Layout did not correctly apply translations to their captions.

In these cases, the system used the original field name instead of the translated value, even when translations were defined. Therefore, the captions were not reflected in the generated output.

This has been fixed. Now, custom field captions correctly use the defined translations when generating documents.

#498888 – The Customer Statement report has been extended to support custom fields in the Overdue section

The Customer Statement report has been extended to support custom fields in the Overdue section.

A new section has been added when using Document Layout V2 to enable users to include custom fields specifically for overdue entries. These fields are now available in the generated output under the relevant Overdue node.

Additionally, descriptions have been added to clarify where sections are applied, making it easier for consultants to configure and understand the layout.

#498775 – Issues arise when importing document layouts exported from older versions of Lasernet BC Connector to newer ones

In previous versions, issues arose when importing document layouts exported from older Lasernet BC Connector versions (4.3.4.1 or earlier) into newer versions (4.4.0.0 or later).

In these cases, imported layouts could default to an incorrect version, and field properties such as Field Name and Field Type were not properly populated. This led to incomplete or incorrect document configurations after import.

This has been fixed. Now, document layouts imported from older versions retain the correct version and field information.

#498064 – When archiving files to Azure Blob Storage using different containers, the system misleadingly indicates success if the Archive and Output filenames are the same

In previous versions, issues arose when archiving files to Azure Blob Storage using different containers for Output and Archive.

When the file name and path were identical in both locations, the system indicated that the file had been successfully archived, even though it had not been moved to the archive container.

This has been fixed. Now, files are correctly archived and validated, ensuring the operation completes as expected.

#497538 – An error occurs when printing and archiving a customer statement with Azure Blob as the Archive option

In previous versions, when printing and archiving a customer statement using Azure Blob Storage, an error occurred, even though the document had been successfully processed and archived.

In these cases, users encountered an error related to content handling, even though the operation completed as expected. This created confusion and uncertainty about whether the document had been properly archived.

This has been fixed. The process no longer generates misleading error messages when archiving customer statements to Azure Blob Storage.

#342207 – The Document Layout page has been enhanced to support exporting and importing multiple layouts at once

The Document Layout page has been enhanced to support exporting and importing multiple layouts at once.

Users can now select multiple document layouts directly from the list and export them into a single file. This simplifies moving configurations between companies or environments without having to manually recreate layouts.

Additionally, document layouts can now be copied directly to another company and imported from the same page, streamlining the overall workflow and reducing setup time.