Skip to main content

D365 FO Connector 6.17.1 Release Notes - News / D365 FO Connector / D365 FO Connector Release Notes - Formpipe Support Portal

May 6 2022

D365 FO Connector 6.17.1 Release Notes

Authors list

LAC365 FO Release Version 6.17.1

Release date: 6th May 2022

This page describes the enhancements in LAC365FO version 6.17.1.

Lasernet version 6.17.1 contains the following models, including the model for the integration with D365CE and the models for the Lasernet print buttons.


ModelDescriptionLocation/remark

Lasernet

Core and main engine for LAC365FO

Lasernet


Requires activation Key

Lasernet > Setup > Parameters > License terms

Lasernet81Spec

Additional requirements in relation to 8.1 and newer versions of standard D365FO


PRNButtons

Lasernet print buttons

Print buttons 

PRNButtonsLACAdaptor

Adaptor between the Lasernet print buttons and Lasernet


LACCE

Provide the integration to CE from LAC365FO

Lasernet > Dataverse/Dynamics 365

LACMSHotfixes

Hotfixes for standard D365FO

System Administration > Setup > Hotfixes from Lasernet

Lasernet Test Suite

Test & Performance Suite

Lasernet > Test and performance suite 


Requires activation Key

Lasernet > Test & performance suite > Parameters

LasernetPU35Spec


Support of Wave labels in D365FO


Please ensure the following new objects/dll-files are added to TFS in case of not just installing/deploying the AOT package (added from LAC365FO version 6.17):

  • LACSupport.dll.config
  • XmlDiffPatch.dll
  • XmlDiffPath.View.dll


Ensure you have the complete list of objects  (not added automatically):

The version number should display version '6.17.1'  after either installing or deploying the AOT-package:

Lasernet > Setup > Parameters

 

Version numbers:

PU49: 6.17.1.2205057

PU50: 6.17.1.2205058           

PU51: 6.17.1.2205059


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

LAC365FO version 6.17.1 is supported with Lasernet version 9, and Lasernet version 10.  A setup for either Lasernet version 9 or Lasernet 10 is required for any new installation and when upgrading from Lasernet 8.

Pre-requisite /   Technical

We recommend making a Stylesheet refresh after upgrading LAC365FO as this could help avoid potential issue(s).

Please also use the following Register selection classes located in LasernetSetupBackup parametersSetup Default Selections in case an error such as the following is thrown when using ExportImport or Copy across companies (legal entities).



The newly introduced upgrade framework in LAC365FO version 6.17 should manage but could ’fail’ in a scenario when using a TFS/Dev build as this would require executing Microsoft.Dynamics.AX.Deployment.Setup.exe.

Error message:

'Please try to run ’Register selection-classes’ before processing.'

OR

'Cannot create a record in Lasernet default export/import selection (LACDefaultSelection). The record already exists.'


Major Enhancements 

Version 6.17.1 only contains fixes and enhancements for LAC365FO and does not contain any major enhancements.

The main focus in LAC365FO version 6.17.1 is 

  • Stability/Quality update for LAC365FO


This is provided through the following enhancements and fixes in LAC365FO version 6.17.1:


Query report with maximum layout should have old format of Output naming, which should contain table name, rather than data source name


Using Maximum for the Layout used the Name (Alias) for the output name of the labels.


Maximum in the Layout property is a similar approach to the versions before LAC365FO version 6.17 and this could cause issues as the naming in previous versions of LAC365FO used the table-names and not the Name (Alias).

LAC365FO version 6.17 does as in older versions use the tablename and not the Name/Alias for the naming of the labels when Maximum is specified in the Layout.


Adding a table like MarkupTrans having the name (Alias) MarkupTrans_SalesTable:


LAC365FO version 6.17 would include the Name (Alias) – MarkupTrans_SalesTable:


LAC365FO version 6.17.1 and previous versions will now use the Tablename - 'MarkupTrans':

Error Message: "The path is not of a legal form"


The following error was thrown when running a Report/Query for which the method productImage() or the method productImageThumbnail() was added within the Query Wizard:

Error message

"The path is not of a legal form. at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths) at System.IO.Path.GetFullPathInternal(String path)"

This is fixed in LAC365FO version 6.17.1.


Group data in files + Subreport 6.17 - only the first report (xml) is correct


LAC365FO version 6.17 had an issue when a report contained a subreport and when Group data in files (splitting of XML-files) was used.

When using the Group data in files:

Would add the values for the subreport from the previous runs and not just for the current one. The first run would be successful, however, the subsequent runs would include information from previous runs.

Adding LACLanguageTextsReportRoot() or  LACLanguageTextsReportRootSubReport() in QW causes an Object reference... error


Using one of the following context methods within the Query Wizard would throw the  following error message:

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

This is fixed in LAC365FO version 6.17.1.


  • LACLanguageTextsReport()
  • LACLanguageTextsReportRoot()
  • LACLanguageTextsReportRootSubReport()

If enums are used in expressions > error 'Value formula is not complete'

Using an Enum within an expression (like in a Condition) could throw the following warning and error:

Warning

"EInvoice is not found in CustTable"

Error message

"Value formula is not complete"


This is now fixed.

Incorrect Purchase Journal being executed when using LAC Print 6.17

Sorting is reverted when resending PurchInquire from std. Journal


The wrong entry/record was selected when resending the report Purchase inquiry and when having multiple entries in the Journal.

When resending the second entry:


would resend the first entry and move the cursor to this entry:


The following warning was thrown when resending from the Archive:

Warning

"Report PurchPurchaseOrderReplacement is not allowed forced rerun On archive or On forms and archive. Skipping report resend"

This is now fixed.


ReturnAcknowledgementAndDocumentTmp issue when attempting to set TempDB record as TMP buffer

Running the report ReturnAcknowledgement in LAC365FO version 6.17 would throw the following error:

Error message

"Table 'ReturnAcknowledgmentAndDocumentTmp' of type TempDB cannot be changed to table of type InMemory."


Random error "Unable to create folder" when using SharePoint 365 for archive

In previous versions, connection to SharePoint could timeout which could cause issues when creating and saving within SharePoint.

The following error message was thrown when using SharePoint as storage (connection):

Error message

"Sending to destination Unable to create folder sites"

This is now fixed.

Error with printing report with three or more data source entities in a class report in 6.17

When Using an OData (Dataverse) Query with more than two data entities in LAC365FO version 6.17, the following error could be thrown:

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


DB Sync issues during LAC 6.17 installation

An index was made unique in LAC365FO version 6.17 to improve performance. However, this could cause an issue when multiple records were resent from the Archive without force-rerun.

The issue was caused when resending more documents from the Archive without a force-rerun, therefore creating multiple entries/records  and conflicting with the unique index:

Therefore, this unique index has been reverted back to non-unique.

 

Non-Cache - issue with table archive

Disabling the Cache for a Report could cause missing values for the Archive (table for Archive) and the mapping fields.

Disabling the cache 

The following warning was thrown after running a Report for which the Cache was disabled (Cache control = Disable cache):


Warning

"Table for archive is not specified or not found.

Customer or vendor account not found, ignoring all customer related destination setups

Customer or vendor group not found, ignoring all customer/vendor group related destination setups

Order Id not found. Archiving with empty order Id

Document Id not found. Archiving with empty document Id"

This is now fixed.

Object reference not set to instance of object Sales person Filter

The following error was thrown when running a report for which SalesTaker (HcmWorker.Name ) was used as a range for the report:

"Object reference not set to an instance of an object. at 

Dynamics.AX.Application.LACQueryMap.`dsChildQueryNamesInit(String dataSourceName) in

 xppSource://Source/Lasernet\AxClass_LACQueryMap.xpp:line 101 at 

Dynamics.AX.Application.LACQueryMap.dsChildQueryNamesInit(String dataSourceName) at

 Dynamics.AX.Application.LACQueryMap.`dsChildQueryNames(Boolean refresh, Boolean @refresh_IsDefaultSet) in

 xppSource://Source/Lasernet\AxClass_LACQueryMap.xpp:line 83 at"

Incorrect language in CE Reports when using an expression

In previous versions of LAC365FO, it wasn't possible to set/overwrite the report language when using an OData (Dataverse) report/query.

LAC365FO version 6.17.1 now supports the option to set/overwrite the Report language when using OData/Dataverse.

Life span processing does not react to max files to process, and the life span destination connection ID choosing was faulty

The Maximum files to process wasn’t respected in previous versions of LAC365FO and Only files that supposed to be moved to storage was not always properly identified. Both of these issues are now fixed.

Bug fixes and Enhancements – LAC365FO version 6.17.1.


Case no.DescriptionTicket no.

296797@LAC365FO

Query report with maximum layout should have the old format of Output naming, which should contain table name, rather than data source name

#25900

296681@LAC365FO

Error: "The path is not of a legal form"

#25857

296406@LAC365FO

Group data in files + Subreport 6.17 - only first report (xml) is correct

#25798 #25882

295854@LAC365FO

Sorting is reverted when resending PurchInquire from std. Journal


296548@LAC365FO

If enums are used in expressions > error 'Value formula is not complete'

#25800

295640@LAC365FO

Incorrect Purchase Journal being executed when using LAC Print 6.17

#25687

295163@LAC365FO


Resend to Predefined destination without force rerun does not work


294706@LAC365FO

LAC 6.17 ReturnAcknowledgmentAndDocumentReplacement error Table 'ReturnAcknowledgmentAndDocumentTmp' of type TempDB cannot be changed to table of type InMemory.

#25494

295395@LAC365FO

Adding LACLanguageTextsReportRoot() or     LACLanguageTextsReportRootSubReport() in QW causes Object reference... error

#25642

295086@LAC365FO

294706@LAC365FO

ReturnAcknowledgementAndDocumentTmp issue when attempting to set TempDB record as TMP buffer

#25494

295079@LAC365FO

Random error "Unable to create folder" when using SharePoint 365 for archive

#25454

294894@LAC365FO

Error with printing report with 3 or more data source entities in a class report in 6.17

#25488

294712@LAC365FO

DB Sync issues during LAC 6.17 installation

#25461

#25678

#25850

293581@LAC365FO

Non-Cache - issue with table archive


293329@LAC365FO

Object reference not set to instance of object Sales person Filter

#24962

293328@LAC365FO

Incorrect Language in CE Reports when using an expression

#25309

296838@LAC365FO

Life span processing does not react to max files to process, and life span destination connection id choosing was faulty




Helpful Unhelpful