Lasernet FO Connector 7.2.1 New Features and Fixes

Lasernet for Dynamics 365 Finance and Operations

Release version: 7.2.1

Release date: 7th October 2025

Introduction

This page describes the bug fixes in Lasernet FO Connector 7.2.1.

The following documentation is available:

• Release notes for Lasernet FO Connector 7.2.1

Bug Fixes – Lasernet FO Connector 7.2.1

Lasernet FO Connector 7.2.1 is released for Dynamics 365 for Finance and Operations versions 10.0.44 (PU68) and 10.0.45 (PU69).

The same source code is used across all versions.

This is a patch release provided through the following bug fixes in Lasernet FO Connector 7.2.1.

485852@LAC365FO – An error occurs when saving a new expense report and adding expense receipt attachments while the Task recorder is on

In previous versions, the following error occurred when the Upload and attach new receipt function was used while creating a new recording with the Task recorder.

This issue has been fixed.

Error

Unable to cast object of type 'Dynamics.AX.Application.TrvExpTable' to type 'Dynamics.AX.Application.DocuRef'.

485381@LAC365FO – Issues arise when using the Mapping and Table for archive fields for the AgreementConfirmationReplacement

In previous versions, the Mapping and Table for archive fields were not populated completely for reports such as AgreementConfirmationReplacement, resulting in the following warnings:

Warning

Lasernet report AgreementConfirmationReplacementUpdating XML Processing Customer or vendor account not found, ignoring all customer related destination setups

Warning

Lasernet report AgreementConfirmationReplacementUpdating XML Processing Table for archive is not specified or not found.

This occurred when either of those fields involved an extended table.

This issue has been fixed.

458824@LAC365FO – An issue arose when trying to access the Tracking functionality unless the user has System Administrator privileges

In previous versions, only users with Lasernet Administrator privileges could access the Tracking functionality for emails, files, Electronic reports in FinOps, and Custom ports.

Custom ports are particularly valuable to deliver and track electronic documents, such as e-invoices, directly to the Peppol network or via a VAN/data provider. It is possible to track end-to-end any documents delivered via Custom ports.

In Lasernet FO Connector 7.2.1, the Tracking functionality can also be accessed by users with Lasernet User privileges.

485245@LAC365FO – The following error occurs when accessing Entity attribute: “A control with the name 'DAZTableBrowserSystemDefined' already exists on the form”

In previous versions, the following error occurred when accessing Entity attribute in Data management:

Error

A control with the name 'DAZTableBrowserSystemDefined' already exists on the form.

This issue has been fixed.

485171@LAC365FO – Error: “A control with the name 'FormButtonGroupControl4' already exists on the form after preview”

In previous versions, the following error message and warning occurred after previewing a report:

Warning

@ApplicationPlatform:ProblemApplyingExtensionLACReportPreview:A control with the name 'FormButtonGroupControl4' already exists on the form after preview

Error

A control with the name 'FormButtonGroupControl4' already exists on the form after preview

This issue also occurred when using Resend > Lasernet Screen, regardless of whether Force rerun had been selected.

This issue has been fixed.

485048@LAC365FO – The correct date format is not applied to the E-mail body parameter when using it through ReportValueFormatted

In previous versions, the correct date format was not applied when formatting a value for a parameter and subsequently using it through ReportValueFormatted.

ReportValueFormatted is used when a formatted output is required, whereas ReportValue retrieves the original, unformatted value.

The issue is illustrated in the following example, where the formatted value is used in an E-mail body.

A parameter value was formatted within the Elements form (structure):

The issue occurred when a reference to the formatted values was used, for instance, within the body of the email by using ReportValueFormatted.

The email body in the XML file did not use the correctly formatted value. This issue has been fixed in Lasernet FO Connector 7.2.1, which uses the formatting applied to the field within the Elements form (structure).

The placeholders have been adjusted for consistency. In version 7.2.1, IDs are now displayed first, whereas they appeared second in previous versions.

A bug affecting lookups performed immediately after adding a field and modifying its Type has also been fixed in version 7.2.1.

484738@LAC365FO – It should not be possible to edit and delete data in Microsoft-hosted environments through Data explorer

Editing and deleting data in Microsoft-hosted (ServiceFabric, Sandbox, and PROD) environments via Data explorer has been disabled in Lasernet FO Connector 7.2.1. However, it remains possible in DEV environments not hosted by Microsoft.

484114@LAC365FO – The ability to add new reports is too narrowly limited to the System Administrator’s role only

In Lasernet FO Connector 7.2, the role of System Administrator was necessary to create a new report. In Lasernet FO Connector 7.2.1, the role of Lasernet Administrator is sufficient to create a new report, query, or class-report (CE).

484043@LAC365FO – All modules included in the software are now listed

All modules (models) are now included within the Lasernet parameters form.