Release version: 6.19.1

Release date: 22nd December 2023

Introduction

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

Click to view the Lasernet FO Connector 6.19.1 Release Notes.

Click to view the Model and Prerequisites page.

Bug Fixes – Lasernet FO Connector 6.19.1

Lasernet FO Connector version 6.19.1 is a patch release for Lasernet FO Connector 6.19 and is released for Dynamics 365 for Finance and Operations version 10.0.36 (PU60), 10.0.37 (PU61) and 10.0.38 (PU62).

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.19.1.

395857@LAC365FO – Exception has been thrown on attempt to register selection classes

The following error used to be thrown in the newer versions of 10.0.38 / PU62 and when either using the class registration or running the install/upgrade tasks.

Normally, the install/upgrade tasks run automatically after an upgrade, but it is possible to run it manually as well.

Class Registration location:

Lasernet > Setup > Backup parameters > Setup Predefined Selections

Install/Update tasks location:

Lasernet > Setup > Parameters

Lasernet FO Connector 6.19.1 will not interrupt the process and will throw the following warning instead.

394096@LAC365FO – SharePoint attachments tuning for specific delivery modes and Graph connections.

The integration with Sharepoint has been optimized by removing some non-required validations of the SharePoint folders.

Previous versions always validated the existence of the folders when using SharePoint as part of the Server configuration.

Lasernet FO Connector 6.19.1 does not validate the existence of the folders in the following situations:

1. Base64 file is used in Report attachments.

2. OriginalURL is used in Report attachments.

3. Graph setup is enabled.

Location: Lasernet > Setup > Administration > Lasernet servers

The following error used to occur in some scenarios when using SharePoint within a multi-threaded environment.

Lasernet FO Connector 6.19.1 is made thread-safe regarding assembly, which is used with SharePoint (.NET 4.7.2).

The following error does not occur anymore, for example when starting a multi-threaded task right after a re-start of the batch-service.

393561@LAC365FO – Different structure in output

Using Same level as parent for the Layout between two tables did not provide the proper output in Lasernet FO Connector 6.19.0.

This has now been fixed.

393528@LAC365FO – Determining file type and MIME type does not work for attachments after the field fileNameOriginal was introduced

In Lasernet FO Connector 6.19.0 MIME type provided the value application/octet-stream, and not application/pdf in the Field/tag-name MailAttachmentFileMimeType.

Attachments would work as expected but could cause an issue in case the value for MailAttachmentFileMimeType was used in other scenarios within Laserrnet (Lasernet configuration), for instance when the Default/demo configuration was adjusted or if used with an electronic document like PEPPOL.

392761@LAC365FO – Wrong XML structure if CustInvoiceTrans is joined to VAT SalesInvoiceTmp record

Adding a child data source (table) for the record containing the VAT transactions from the table SalesInvoiceTmp would not always create the proper structure for the XML file.

This used to happen in situations in which the reference value in LACTransRefRecId was 0 and when LACTransRefRecId was used as a part of a relation.

In the following example LACTransRefRecId is used as the relation between the tables SalesInvoiceTmp and CustInvoiceTrans.

Adding a sub-query used to include all records.

392439@LAC365FO – Subreport parameters Ranges Lock: 1 1 Value formula is invalid. Please refresh style sheet to update formulas in report

The following warning was thrown when importing a report containing a sub-report for which some of the ranges were locked.

Everything would work as expected. However, the warning has been removed in 6.19.1.

391983@LAC365FO – Exception has been thrown by the target of an invocation. queryBuildDataSource object does not have the right table Id

The following error occurred when exporting or copying a report for which not all tables existed in the chosen environment.

Lasernet FO Connector 6.19.1 will now throw an error about the unknown tables.

The following error was thrown when opening a condition for a section or an element within the structure, and if tables or fields did not exist:

Lasernet FO Connector 6.19.1 will show a prompt such as the following in case the condition for the query contains non-existing tables or fields.

This allows to reset the Query and then open the Filter.

388862@LAC365FO – LACReportNameFinderData::parmCallStackDataMember() returns an array, but a list is expected

The following error used to be thrown when the Report name finder was used for a customized report.

This has been fixed.

388343@LAC365FO – Errors when importing query exported from 6.19 with unknown sorting field

Importing a report for which a sorting field did not exist within the database used to cause one of the following errors:

or

Lasernet FO Connector 6.19.1 will replace the unknown fields with the RecId-field and show the following error

388331@LAC365FO – XML structure changes unintendingly by using query wizard on a Subquery

Using the option to convert a sub-report into the query/sub-query caused sections to be renamed if the existing sub-report was not deleted (1 was added as a postfix).

Lasernet FO Connector 6.19.1 will try to retain the naming of the section. However, it is best practice to remove a sub-report once it has been converted into the query/sub-query.

Using the conversion of a sub-report without removing the existing sub-report could cause an issue with the naming of sections.

Converting a sub-report into the query/sub-query could cause a renaming of the section when finishing the Query Wizard.

Converting a sub-report:

After converting into a sub-query:

This could cause the name of the section to be changed when adding additional tables and fields within the Query wizard and after finishing the Query wizard.

388182@LAC365FO – Error when executing expression, Invalid expression projection

Additional brackets were required in Lasernet FO Connector 6.19.0 when using selection statements (for example, “IF”-statement).

The following error was thrown after executing a query/report in case the additional brackets were not added.

These additional brackets are no longer required.

To avoid this error, add in brackets.

The following expression:

If CustTable.customerGroup() = "Retail customers2" then "Customer group: 30 - Retail customers"

else if CustTable.LanguageId() = "de"     then "German"

else if CustTable.LanguageId() = "en-US" then "English"

else if CustTable.LanguageId() = "da"     then "Danish"

else if CustTable.LanguageId() = "fr"     then "Frence"

else "default"

387733@LAC365FO - Lasernet FO Connector 6.19 is affecting standard dimension filtering

Descriptions such as Name, Description, etc. were not properly shown in Lasernet FO Connector 6.19.0, when looking up one of the Dimension-fields within the range for a query.

For example, when creating a Payment Proposal in which only the Record-ID was shown.

385931@LAC365FO – Roles other than System Administrator are unable to access the LACStartup menu item when AllowRootNavigation is set to “No”

The following error was thrown when using LACStartUp as part of the URL, and when the user did not have System administrator priviledges.

Lasernet FO Connector 6.19.1 does not require the System administrator role anymore.

Using &mi=LACStartup as part of the URL is useful as it provides the option to create shortcuts, which can contain additional arguments/parameters that can get parsed and used within any of the reports in Dynamics 365 Finance and Operations and for any of the query/replacement-reports within the Lasernet FO Connector.

For instance, with a location/pick-zone, it is possible to parse a Printer/Default printer which should be used when Dynamics 365 Finance and Operations is started from a shortcut at this location/pick-zone.

https://dynamics365fo/?cmp=USMF&mi=LACStartup&Defaultprinter=Warehouse_printer_1

383327@LAC365FO – An Issue where the quantity is not being filtered when there are more than 2 places after the decimal point - ##,## works but having ##,###, or more does not work.

Using a range for a sub-report did not return all records when the values contained more than two decimals (digits/decimal places).

Such as where the quantity for a BOM-line was used as part of a range.

The Quantity field was used as a range for the sub-report and performed as expected until it had more than two decimals.

Records having more than two decimals would not beincluded in the sub-report.