Lasernet FO Connector 6.21.2 New Features and Fixes

Lasernet for Dynamics 365 Finance and Operations

Release version: 6.21.2

Release date: 19th September 2024

Introduction

This page describes the fixes and enhancements in Lasernet FO Connector 6.21.2.

The following documentation is available:

• Release notes for Lasernet FO Connector 6.21.2

Fixes and Enhancements – Lasernet FO Connector 6.21.2

Lasernet FO Connector 6.21.2 is released for Dynamics 365 for Finance and Operations version 10.0.39 (PU63), 10.0.40 (PU64), and 10.0.41 (PU65).

The same source code is used across all versions.

This is aimed to be a quality update, provided through the following fixes and enhancements in Lasernet FO Connector 6.21.2.

439140@LAC365FO – An Object reference error occurred when using the Expression and Range functions

The following Object error occurred in newer versions of 10.0.40 (Update64) and 10.0.41 (Update65).

The issue was caused by a System Enum, which was exposed in standard Dynamics 365 Finance and Operations starting from 10.0.40 but was not fully implemented by Microsoft.

The issue occurred when entering an Expression after clearing the cache in Lasernet FO Connector, as the Connector attempted to rebuild the cache after it had been cleared.

This incomplete Enum will disrupt the cache-rebuilding process.

The same error occurred when using an Expression for a Range:

Lasernet FO Connector 6.21.2 detects this problem and issues a warning if a system Enum is not fully implemented.

We expect this Enum to be fully implemented in Dynamics 365 Finance and Operations 10.0.42 (Update 66), but we will keep this detection device in the coming versions of the Connector.

433689@LAC365FO – The option to disable the validation of the date fields From and To in standard Dynamics 365 FO is now available

Lasernet FO Connector 6.21.2 includes a preference to disable the validation of the From/To date option within standard Dynamics 365 Finance and Operations.

This is a useful enhancement for accessing data such as the address/global address book, which normally uses the current date to determine if a record is valid.

Activating the new property, Ignore default valid time state, causes the system to bypass the validation of the From/To date option.

In the following example, a dialog field is set up with a date that will be used for the Ranges:

The dialog field is used for the Range:

Executing the report with the Ignore default valid time state option turned off:

No output is generated because the default Ignore default valid time state is disabled, and standard validation against current dates will, therefore, also be applied.

Enabling Ignore default valid time state:

The output is generated because Ignore default valid time state is enabled, which causes the system to bypass the standard validation and only apply the one used in the Ranges for the Query.

433688@LAC365FO – The assembly load has been reduced in Lasernet FO Connector 6.21.2 when using replacement (Query) reports

The assembly load has been reduced when using replacement (Query) reports.

However, there are still issues when running standard SSRS reports or using standard reports (Queries) and SSRS as the source for the Lasernet report, as the number of assemblies increases.

This memory issue is resolved only by restarting or recycling the service, which frees up the memory within the AppDomain: the memory in the Loader Heap will not be freed until the environment restarts or recycles.

Microsoft is investigating this matter and should provide a fix within a newer update of Dynamics 365 Finance and Operations.

When using SSRS or SSRS as the source for the Lasernet reports, the memory in the Loader Heap will keep rising until the environment restarts or recycles:

When using replacement reports (Query) in Lasernet FO Connector, the count of loaded assemblies and memory usage in the Loader Heap remain stable:

The problem with standard SSRS reports and SSRS reports being used as the source for Lasernet reports may be connected to Microsoft's ReportingServicesService.exe.

The following example is taken from a standard Dynamics 365 for Finance and Operations Tier-1 environment, and additional details will be provided for Tier-2 and higher environments.

The ReportingServicesService.exe comprises a large number of assemblies (types), and the bytes in the Loader Heap for the Reporting service increase with each report execution.