Lasernet BC Connector 4.4.0.3 New Features and Fixes

Lasernet for Dynamics 365 Business Central

Release version: 4.4.0.3

Release date: 12th January 2026

Introduction

This page describes the bug fixes in Lasernet BC Connector 4.4.0.3.

The following documentation is available:

• Release notes for Lasernet BC Connector 4.4.0.3

Bug Fixes – Lasernet BC Connector 4.4.0.3

Lasernet BC Connector 4.4.0.3 is a quality update provided through the following bug fixes.

#493916 – Placeholder Sets resolve to incorrect values when using data from sales invoices

In previous versions, Placeholder Sets used in Email Templates resolved to incorrect values when using data from sales invoices. In some cases, the salesperson's information included in the generated email did not match the salesperson on the invoice.

This issue has been fixed, ensuring that placeholder values correctly reflect the sales invoice data.

#493936 – An error message appears when sending customer statements using Azure Blob as the Lasernet Archive

In previous versions, an error message could appear when sending customer statements via email while using Azure Blob as the Lasernet Archive, even though the email was sent and the document was archived successfully.

This issue has been fixed. Customer statements can now be sent without receiving any unnecessary error messages.

#493937 – The Lasernet Archive option is not visible on the Customer list and Customer card when Azure Blob is selected

In previous versions, the Lasernet Archive option was not visible on the Customer list and Customer card when Azure Blob was selected as the archive type in Lasernet Setup.

This issue has been fixed. The Lasernet Archive option is now available regardless of the selected archive type.

#494438 – The Lasernet BC Connector upgrade fails if no Lasernet Connector Setup record exists

In previous versions, the Lasernet BC Connector upgrade could fail if no Lasernet Setup record existed for the selected company. This could affect customers upgrading from versions prior to 4.4.0.0.

This issue has been fixed. The upgrade process now completes successfully even if a setup record is missing.