LAC365FO Release Version 6.14.0

Release date: 4th June 2021

This document describes the enhancements in LAC365FO version 6.14.0.

Lasernet version 6.14.0 contains all the models including the model for the integration with D365CE and the models for Lasernet print buttons.

The newly introduced package LACMSHotfixes contains hotfixes for the standard D365FO.

It is possible to install/deploy this package separately and the package will get updated once new hotfixes are introduced for the standard D365FO.

Both the package and the release notes for LACMSHotfixes are accessible as separate downloads.

New model LasernetPU35Spec

The new model LasernetPU35Spec is added for supporting the Wave labels in standard D365FO.

The model LasernetPU35Spec is only added to the PU34+ package and it’s possible to download and install a separate package containing this model.

LAC365FO version 6.14.0 is only supported from Lasernet version 9 and a setup for Lasernet version 9 is required for any new installation and when upgrading from Lasernet 8.

The version number should contain version 6.14.0 such as the following after either installing or deploying the AOT package:

Lasernet > Setup > Parameters

Add the AOT-package:

• Either through LCS - apply a deployable package to an environment 

https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/deployment/apply-deployable-package-system 

• Or by installing a deployable package – requires RDP access to the environment 

https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/deployment/install-deployable-package

Major enhancements

The primary focus in LAC365FO version 6.14.0 is stability and usability.

LAC365FO version 6.14.0 supports Dynamics 365 for Finance & Operations PU43 (10.0.19).

Using previous versions of LAC365FO would cause issue(s) with PU43 (10.0.19) as the Lasernet destination wasn’t shown for all reports – both an issue with the printer settings dialog and the Lasernet print buttons.

Stability

Support for PU43 (10.0.19)

Support for Dynamics 365 for Finance & Operations PU43 (10.0.19).

LAC365FO contains the new option Auto detect patterns.

The Lasernet connector (LAC365FO) is using the “call-stack” in std. Dynamics 365FO to identify if Lasernet should be available as the destination.

This call-stack is changed in standard Dynamics 365FO PU43/10.0.19 and therefore also requires changes in LAC365FO (and PRN as well).

The feature Auto detect patterns within Lasernet > Setup > Parameters are added to support any versions of Dynamics D365FO. – Basically to ensure LAC365FO are both backward and forward compatible.

Please use the Auto detect patterns in case the Lasernet destinations aren’t shown as expected.

It will automatically get initialized when running a report for the first time, but requires a “re-initialization” by using the Auto detect patterns when upgrading to Dynamics 365 for Finance & Operations PU43 or newer.

Information about the detection of Lasernet as a destination is saved within the fields Stack form pattern and Stack class pattern.

Please remember to use the Auto detect patterns for each of the Companies/Legal entities within Dynamics 365 for Finance & Operations in case Lasernet is missing as a destination or in case of an upgrade to D365FO PU43 or newer.

Auto detect patterns are located in Lasernet > Setup > Parameters

The Stack form pattern and Stack class pattern are made visible to provide an option for a work-around in case Microsoft makes additional changes to the “call-stack” in future versions of Dynamics 365 for Finance & Operations.

Optimized form links

Previous versions of LAC365FO did save a copy (packed version) of the Query which was created within the Query Wizard.

This could cause issue(s) when adjusting the structure within the Query Wizard as this could change the Unique IDs which are used for the ranges within the Form-links.

A new approach has been implemented in LAC365FO version 6.14 which is re-using the same Query as the one created within the Query Wizard and only applies the ranges and the sorting when used in the Form-links.

Please delete the “last-values” in case a report isn’t working as expected.

Example of the issue in previous versions

Start by having a structure in which CustTable is the top-most parent data-source/table and CustTrans is the child data-source/table.

Use the field CustTable.AccountNum to link a Form with the Query – like the following:

Revert the structure within the Query Wizard, use the table CustTrans as the highest parent data-source/table and use the table CustTable as child data-source/table.

This would remove the Range for custTable.AccountNum – the ranges for CustTable.AccountNum would get lost within the Form-links.

LAC365FO version 6.14.0 will keep the range(s) – like the range CustTable.AccountNum in the following:

Usability / Simplicity

Adding images/pictures

A new option for adding images such as company logos is added into LAC365FO version 6.14.0.

It’s possible to add the pictures/images (overlays) at the following locations 

• Lasernet > Setup > Lists > Images
• Lasernet > Common > Reports
• Lasernet > Setup > Lists > Report group

Lasernet > Setup > Lists > Images

The general location for adding images which afterward can get used at Report-level and/or in the Report group(s).

Lasernet > Common > Reports

Images are added specifically for the report.

It creates a report group containing a range for the specific report (Dynamic Range for the report) and the added image(s).

Lasernet > Setup > Lists > Report group

Provides the option to add images across a number of reports 

Images are added (binary encoded) into the XML file such as the following:

They can get used in Lasernet by using Image > Job > Base64.

Bug fixes and enhancements

220677@LAC365FO – Query version (QueryWizard vs FormLinks vs Last Value) miss-match produces various unpredicted results.

220934@LAC365FO – Check report query Last values affect between multiple Form links and Dialog defaults.

A version of the Query is no longer saved within the Form links. 

This approach is used to ensure existing ranges are kept for the Query within the Form links after modifying the Query within the Query Wizard.

220765@LAC365FO – Validate enum value on the parameter

A warning such as the following is displayed in LAC365FO version 6.14.0 when entering a non-existing value for an Enum:

Note: It was possible in previous versions of LAC365FO to enter a non-existing value for the Enum.

LAC365FO version 6.14.0 will display a warning similar to the following when entering a non-existing value for an Enum:

No validation of the Enum-value when Range is marked

No validation of the Enum-value when Validate is disabled

220766@LAC365FO – Batch execution does not have LACReport initialized when running CE(class) reports

In previous versions of LAC365FO, it was not possible to execute an OData report within a batch task.

LAC365FO version 6.14.0 supports the option to use a batch-task for an OData-Query (CE).

Executing an OData-Query (CE) within a batch task would throw the following error:

Error

'Batch task failed: Object reference not set to an instance of an object.'

220807@LAC365FO – Unable to lookup ODATA field values, when field property is different from field name

Making a lookup of OData fields didn’t work as expected when the field property was different from the field name - such as having a field-entity accountId for the entity quotes.

This is fixed in LAC365FO version 6.14.0.

Error

'Failed to get OData.'
 'Bad Request quotes?$select=accountid Error code: 0x0 Message: Could not find a property named 'accountid' on type 'Microsoft.Dynamics.CRM.quote'.

220971@LAC365FO – Adding custom(yellow) OData field is not initializing right data type, as fields are taken only from selected fields in the wizard

The Type/Datatype when adding an element manually for an OData-Query wasn’t set to the proper type, such as in the following in which the Type/Datatype should become a Real.

Only an issue when using an OData-Query and work-around was manually adjusting the Type/Datatype.

The Type/Datatype are set properly in LAC365FO version 6.14.0.

Previous versions of LAC365FO

LAC365FO version 6.14.0

221048@LAC365FO – Lookup of SharePoint subsites is limited to 99

220160@LAC365FO

Previous versions of LAC365FO did only support lookup for 99 subsites when using Sharepoint within the connection for a server.

LAC365FO version 6.14.0 supports an “unlimited” number of subsites. 

221103@LAC365FO – Image list for Lasernet reports

A new option for adding images like the company logo is added into LAC365FO version 6.14.0.

It’s possible to add the pictures/images at the following locations:       

• Lasernet > Setup > Lists > Images
• Lasernet > Common > Reports
• Lasernet > Setup > Lists > Report group

221384@LAC365FO – Validation on orphaned LACReportParameters

Activating the following preview feature could cause issues when saving the record at a Form.

It could also cause issues when trying to add a condition to the Form.

The Work-around was disabling the following preview feature in std. Dynamics 365 for Finance & Operations.

Warnings such as the following could get thrown in Form Lasernet servers when trying to create/save the record:

Warnings

'Field 'Instance' must be filled in.'

'Field 'Connection string' must be filled in.'

The following warnings could get thrown when adding a condition:

Warning(s)

'Field 'Label' must be filled in.'

'Field 'Section' must be filled in.'

'Field 'Report' must be filled in.'

221459@LAC365FO – EcoResProductCategory somehow is referenced in Retail and in PU43 requires Lasernet reference to Retail

A reference to the model Retail is required for the model Lasernet when using Dynamics for Finance & Operations PU43 / 10.0.19.

This is added in LAC365FO version 6.14.0.

221478@LAC365FO – Error on validation of report type class

Validating a report of type Class (OData/CE) could throw an object reference error. Refreshing the meta-data could avoid this error.

This is fixed in LAC365FO version 6.14.0.

Error message

'Object reference not set to an instance of an object.'

221538@LAC365FO – Validation on License expiration fails on older kernels (PU3)

The following warning was displayed when opening either the Form Lasernet reports, Lasernet parameters or when processing a report and when having an expiration date for the license. The warning was shown even though the Expiration warning was set as low as it shouldn’t throw the warning. – such as when using an open demo license having an Expiration date:

This is fixed in LAC365FO version 6.14.0.

221912@LAC365FO – Empty screen after review and after applying a signature to a document

An empty screen was shown after delivering a document for which a signature was added within the review of the document.

This is fixed in LAC365FO version 6.14.0 and no empty screen is shown after delivering a document containing a signature.

Bug fixes and enhancements