---
title: "Lasernet BC Connector 4.3.4.0 New Features and Fixes"
slug: "lasernet-bc-connector-4340-new-features-and-fixes"
description: "This page provides a detailed overview of the bug fix brought to users by Lasernet BC Connector 4.3.4.0. Read for more information."
updated: 2026-02-26T17:06:51Z
published: 2026-02-26T17:06:51Z
canonical: "kb.lasernetgroup.com/lasernet-bc-connector-4340-new-features-and-fixes"
---

> ## 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.3.4.0 New Features and Fixes

## Lasernet for Dynamics 365 Business Central

**Release version: 4.3.4.0**

**Release date**: 7th April 2025

### Introduction

This page describes the bug fixes in [Lasernet BC Connector 4.3.4.0](https://support.formpipe.com/downloads/files/lasernet-bc-connector-4340).

[Release notes for Lasernet BC Connector 4.3.4.0](/v1/docs/lasernet-bc-connector-4340-release-notes) are available.

### Bug Fixes – Lasernet BC Connector 4.3.4.0

Lasernet BC Connector 4.3.4.0 is a patch release provided through the following bug fixes.

#### #460991 – The Show Price on Shipment option inherits its settings from the Customer Card by default

In previous versions, the **Show Price on Shipment** option did not inherit its setting from the Customer Card when opening the shipment report request page. This has now been fixed: the **Show Price on Shipment** feature behaves the same way as the existing **Default Print Method** logic, ensuring the user’s preference on the Customer Card is correctly applied to the report request page.

#### #461014 – Statement reports do not reuse email properties from previous customers anymore

In previous versions, when sending a statement report using a customer’s details, the email properties (including the email address) were incorrectly carried over from the first customer to the following one. This occurred because the report’s settings retained values from the last run. The logic has now been updated so that each new run pulls fresh email properties based on the current customer, ensuring the correct email address is used every time.