---
title: "Lasernet Business Central Connector 4.4.0.6 Release Notes"
slug: "lasernet-bc-connector-4-4-0-6-release-notes"
description: "This article briefly describes the bug fix in Lasernet BC Connector 4.4.0.6. Read for more information and the link to the installation packages."
tags: ["Business Central", "Lasernet BC Connector", "Release notes"]
updated: 2026-05-01T10:25:19Z
published: 2026-05-01T10:25:19Z
canonical: "kb.lasernetgroup.com/lasernet-bc-connector-4-4-0-6-release-notes"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lasernet BC Connector 4.4.0.6 Release Notes

## Lasernet for Dynamics 365 Business Central

**Release version: 4.4.0.6**

**Release date**: 1st May 2026

### Notes

[Software installation files](https://support.lasernetgroup.com/downloads/files/lasernet-bc-connector-4406) are available.

> [!WARNING]
> Warning
> 
> The Lasernet Connectors for Microsoft Dynamics 365 are currently not compatible with Lasernet Core 11. 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.

### Maintenance Report

This section briefly describes the bug fix in Lasernet BC Connector 4.4.0.6.

#### New Features, Fixes, and Enhancements

| Internal Ref. | Issue/Feature | Details | Status |
| --- | --- | --- | --- |
| 505218 | Custom fields are mistakenly translated twice. | In previous versions, custom fields were mistakenly translated twice. This caused a length validation error for strings exceeding 100 characters, preventing reports from generating successfully. This hotfix resolves the issue by removing redundant calls, ensuring the translation text is not translated twice during processing. Additionally, a new **Skip Translation Attribute** setting has been added to the **Document Layout** field. Enabling this prevents the translation attribute from being added to the XML node, enabling consultants to omit redundant text when the **Description** and **Value** fields are identical. | Bug fix |

> [!WARNING]
> Warning
> 
> We are aware of the existence of a bug, tracked under item #505294, that causes an error in **Document Layout V2** stating "The given key was not present in the dictionary".
> 
> This happens if an active field no longer exists (for example, when linked to a deleted app) or if the **Skip if Empty** feature is enabled for an empty field.
> 
> The current workaround for this bug is to deactivate the affected fields or turn off the **Skip if Empty** feature.

### **How to Get Support**

If you encounter difficulty using Lasernet BC Connector, contact [Lasernet Support](https://support.lasernetgroup.com/new-ticket).