Lasernet Connector for Dynamics 365 Finance and Operations Release Version 6.17.0

Release date: 1st April 2022

This page describes the enhancements in Lasernet FO Connector 6.17.0

Lasernet FO Connector 6.17.0 contains the following models - including the model for the integration with Dynamics 365 Customer Engagement and the models for the Lasernet print buttons.

Ensure the following new objects/dll-files are added to TFS in case of not just installing/deploying the AOT-package.

• LACSupport.dll.config

• XmlDiffPatch.dll

• XmlDiffPath.View.dll

Ensure the following list of objects are added (they are not automatically added):

The version number should contain version 6.17.0  after either installing or deploying the AOT-package.

Lasernet > Setup > Parameters

Version numbers:

• PU48: 6.17.0.2204018

• PU49: 6.17.0.2204015           

• PU50: 6.17.0.2204017

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

Lasernet FO Connector 6.17.0 is supported with Lasernet version 9 and Lasernet version 10 and a setup for either Lasernet version 9 or Lasernet 10 is required for any new installation and when upgrading from Lasernet 8.

Lasernet FO Connector 6.17 contains an option to reduce record-size in the Archive as this could become quite large.

Reducing the size would still keep the documents (PDF/XML) within the Archive but would remove the information required for resending a document from scratch from the Archive (the force-rerun option).

It would still be possible to resend the document(s) from the standard Journal.

Deleting or shrinking the archive can reduce the DB/record-size significantly.

– see the following section in relation to the option to shrink/delete information in the Archive.

Pre-requisite / Technical

It is best practice to do a Stylesheet refresh after upgrading Lasernet FO Connector as this could help avoid potential issue(s).

Please use the following Register selection classes located in Lasernet > Setup > Backup parameters > Setup Default Selections in case an error such as the following is thrown when using Export, Import or Copy across companies (legal entities).

The newly introduced upgrade framework in Lasernet FO Connector 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 – Lasernet FO Connector 6.17.0.

Lasernet FO Connector 6.17 contains many new features including features that can assist in improving performance.

The Connector itself has been optimized in relation to performance but Lasernet FO Connector 6.17 also contains features that can lower the content of the XML-file and therefore optimize performance.

Main focus in Lasernet FO Connector 6.17 

• Performance

• Reliability 

• Usability (user-experience) and Flexibility

• Simplicity

This is provided through the following major enhancements in Lasernet FO Connector 6.17:

Performance

• Time for the report execution has been optimized 

• Performance in Archive is optimized

• Query Wizard is much faster 

• Lower use of memory 

• New features in Query Wizard to assist in lowering size of XML-file

• Autoconversion of subreports into Query structure

Reliability

• Automatic backup (option to schedule export)

• Compare functionality

• Auto update of Lasernet design (in case Output is restructed)

Usability and Flexibility

• Query Wizard

  • Improved search option 

  • Option to Copy, Move data-sources

  • Query links (master query) 

  • Better options for labels and language texts

  • Better options to structure the output (XML-file)

• Autoconversion of subreports into Query structure

• Autocreation of Design document

Simplicity

• Attachments (Attachments and entries from Archive)

Query Wizard (overview)

The following information contains an overview of the new features which have been added to the Query Wizard.

Examples of new features are provided at the end of this page.

Top Bar

Copy/Link Query

Provides the option to either copy or link to another Query.

Using a link to a Query provides the option to maintain and use one central Query – like a Query for the CompanyInfo.

The performance is also greater compared to using a subreport.

Copy/Move

Provides the option to copy or move the datasources – including the option to include all nested data sources.

Useful when there’s a need to re-structure datasources (tables) within an existing structure and also useful when there’s a need to insert table(s) in-between existing tables.

Autoconversion of Sub-report

It’s possible to automatically convert an existing Sub-report into the Query. 

This feature is located within the structure/element of the report – Lasernet > Common > Reports > Structure.

The advantage is better performance especially if the sub-report is used at line level as this would cause the sub-report to be executed numerous times.

Executing a sub-report multiple times would cause many ”round-trips” and could cause slower performance.

Query links contain a nice overview of where the sub-report(s) and a ”query-link(s)” are used.

Sub-reports and Query-links

Labels

Provide the option to add multiple labels within the Query Wizard.

Data sources 

Properties when selecting Data sources

Parameters

Provide the option to include the parameters from either the SSRS/Replacement-report or from fields created through the Dialog setup within the Output (XML-file).

Useful in case parameters for initializing the report should get shown as part of the document – such as when there’s a requirement for showing the Account-range, Date-range, etc. which was used when running the Report.

It’s best practice to provide the option to show which ranges have been applied when a report was executed, especially if it’s an internal or a statistic report.

Language texts

Provide the option to include the labels/language texts which have been added through the Report group (this would basically add the previously used context method LACLanguageTextsReport().

Layout

Provide the option to specify what should get included in the Output/XML-File (Min, Medium, Maximum).

This is extremely useful when there’s a need to optimize performance as it can lower the size of the XML file by using Minimum instead of Maximum.

It can especially improve performance when having a report with many details/records/lines.

Using Minimum instead of Maximum in Layout would require adjustment of the Lasernet design, but Lasernet FO Connector 6.17 contains a new feature that provides the option for converting the Lasernet design (pattern and re-arranges).

The default for the Layout when creating a new report (Query) is Minimum.

The default when creating a replacement report is Maximum.

Labels

Provide the option for adding multiple labels and language texts for a specific Query.

Adding the labels or language texts for a specific Query is also shown at the Data sources (top level).

Query

Properties when selecting a Query

Create element

Option to specify if the Query name should get added into the XML file.

Create element is automatically enabled when converting a sub-report into the Query structure as this would ensure the same structure as when the sub-report was used.

Show labels on

Option to specify where and how often labels should get shown within the XML file.

Normally a label only is required one time within a document and having a lot of repeating labels could harm performance.

Show Labels on has been introduced to avoid repeating labels but can also ensure all labels are shown by using the Top-option, such as where there’s a need for always showing a label even though no record exists.

Labels

Provide the option for adding multiple labels and language texts for a specific data source.

Labels or language texts added for a specific data source are also shown at Data sources (top level).

Search for field names

Searching for field names now contains two options:

• Search for field name across all data sources/tables (like in previous versions)

• Search for field name within a specific table

These new search options apply to the following areas:

• When adding fields

• When adding sort fields 

• When adding field(s) for a range

It’s possible to toggle between the two search options by using the following button:

The following image illustrates when searching across all data sources/tables:

The following image illustrates searching within a specific data source (table) but it is possible to select any of the data sources/tables within the dropdown for the table name:

Attachments (simplified)

Working with attachments has been improved and now supports adding attachments at the line/detail level and now doesn't require the use of context methods.

It is also possible to add existing documents from the Archive and it's possible to specify if All, Last or only the First attachment/archive document should get added.

Attachment from

From attachments

From attachments will add the attachments (DocuRef / DocuValue) from the table specified in Attachment reference table.

Also works with attachments located at detail/line-level and therefore no need as in previous versions of Lasernet FO Connector to add a context-method.

Detail/line-level is like when having the need for adding attachments from like Sales lines (SalesLine), Confirmation lines (CustConfirmTrans), Invoice lines (CustInvocieTrans) etc.

From attachments

From attachments are useful when having the need for adding existing document(s) from the Archive such as when adding Customer invoices (Sales-invoice) when running the Report CustAccount-statement.

Reserved

Used with the context methods and doesn't require/respect any setup for the attachment(s) as this is managed through the context method itself. 

Attach

All

This will (for the table specified in Attachment reference table) add all attachments or all documents from the Archive which meet the specified criteria (Restriction, Type and condition).

Last

This will (for the table specified in Attachment reference table only) add the last attachments or last Document from the Archive which meet the specified criteria (Restriction, Type and condition). 

First

This will (for the table specified in Attachment reference table only) add the first attachments or first Document from the Archive which meet the specified criteria (Restriction, Type and condition).

Backup / Scheduled backup

Exporting from either Lasernet > Common > Backup > Export Lasernet Backup or from Lasernet > Common > Reports > Export report Backup now contains the option to schedule this export and to use a storage type such as Azure Storage, File-system, Sharepoint, etc. for the export.

It’s also possible to enter a static file name which is useful, as this provides the option to schedule a  backup that can get automatically imported into other environments (s) – such as when there’s a need to ensure multiple environments are in-sync/updated. 

It’s possible to use a static file name in the source environment and schedule a backup every night at 03:00 which is imported at 04:00 to the destination by using this static file name.

A new option Dynamic is introduced in relation to the Import. Dynamic will ensure the file isn’t imported unless it exists.

Follow these steps as an example of exporting to Azure Storage (Source):

1. Select the Lasernet Connection within the field Endpoint type and select a connection in the dropdown for Connection.

2.  The Export is compressed with the fixed name SyncUpEnvironments (see settings in the image below). Save the Export in the location which is specified Azure Storage.

3. Specify which reports to include and click Ok

The option Lock to pre-defined selection provides the ability to save the selection(s) as default for the next time it is used – in this case it would get saved for the Default.

4. Enable Batch processing and use Recurrence to specify the recurrence/schedule of the batch.

The following settings would ensure an export every night at 03:00:

Example – Automatic import (destination):

Comparing Query definition

Lasernet FO Connector 6.17 contains a new powerful option for comparing ’files’.

Currently, this is introduced at report level and within the Archive where it’s possible to compare either two query definitions or compare two entries in the Archive.

This is useful when there’s a need to compare between an older and newer version of a Query such as when having a backup of a Report/Query which could get compared with the new definition.

This can also get used for version control and documentation as long as the query exists as a copy or backup.

It is possible to make a copy of a report/query before making any adjustments and then after the adjustment use the compare tool to illustrate/describe what has been modified. 

This version contains a new feature that can create a Report-summary (FDD).

Compare queries

This feature works for replacement reports (query) and brand new queries but not for SSRS reports.

The feature is located in Lasernet > Common > Reports.

You must select the two queries which will get compared and then click Compare

The following image demonstrates when the Query SalesConfirmReplacement is compared with the backup SalesConfirmReplacement_Backup:

The following image illustrates when having a different definition for the queries such as tables, fields, sorting, ranges, etc.:

A similar option exists for the Archive in which it is possible to compare two entries within the Archive – Lasernet > Common > Reports > Journal (Archive)

The user must find two entries in the Archive and select Compare.

This would compare the two XML files within Archive:

Optimize Lasernet Log

The entries within the Lasernet Archive contain the information required for resending when using the option Allow force rerun.

Force rerun would ensure the document(s) is re-initialized/created from the start and would ensure document(s) (normally PDF file) aren't picked up from the Archive.

This information is packed in a field/record within the Archive which often requires quite a lot of ”space”.

Lasernet FO Connector 6.17 contains an option to shrink or completely remove this information within the Archive.

This will lower the size of the Archive but keep the existing and saved documents (PDF / XML) in the Archive.

It’s possible to avoid information only used for the resend with force rerun to get saved by disabling the option for force-rerun.

The following two options for Allow forced rerun will save the required information for the force-rerun:

• On archive

• On forms and Archive

The required information for ’force-rerun’ is saved within the Archive.

Lasernet FO Connector 6.17 does show the size of the record used for the resend data – such as the following.

Using the values <Empty> or On forms in Allow forced rerun will not save the information required for the force-rerun:

It would not be possible to use the force-rerun option in case <Empty> or On forms are specified in Allow forced rerun. Force-rerun will work from standard journals even when deleting the resend data.

Force rerun is still shown in the standard journal:

It is the same if deleting DELETE RE-PROCESSING DATA (LACARCHIVERESENDDATA):

The initial size of the created records is lowered in Lasernet FO Connector 6.17 and would also get lowered when ’shrink’ is used.

The option to either delete or shrink the Archive is located in Lasernet > Setup > Parameters:

Either select the DELETE RE-PROCESSING DATA (LACARCHIVERESENDDATA) or use the SHRINK RE-PROCESSING DATA (LACARCHIVERESENDDATA).

The value in the field Archive age (in days) indicates how old (in days) the archive must be to delete re-processing data for it.

It is also possible to run across all companies/legal entities by using the option Cross company.

A similar option to delete/shrink the Archive is located within the Archive. The option located within the Archive is useful in case of testing the size of a record before and after shrinking the records:

Support for Force rerun before deleting the resend data:

Use DELETE RE-PROCESSING DATA (LACARCHIVERESENDDATA).

This will remove the option for force-rerun and still provides the option to resend the existing document within the Archive (Normally a PDF file).

Autocreation of Design Document

Lasernet FO Connector 6.17 contains a powerful option for creating a design document (FDD).

This is useful for preparing both a nice overview of the reports and for preparing documentation.

This feature is located at the report level – Lasernet > Common > Reports.

Select the required report followed by Generate report summary.

This prepares the following document (Excel file) containing the report summary:

The field Documentation mapping column located in the structure/elements for the report provides the option to specify a reference to the design in Lasernet.

This would get added to the document (EXCEL file) such as the following:

Auto-conversion of Lasernet Design

Changing the structure of the Output (XML-file) could also require adjustments of the design in Lasernet, such as in relation to the patterns (details) and re-arranges that are used.

Lasernet FO Connector 6.17 contains a new feature that automatically converts the Lasernet design (patterns and re-arranges). This can happen when changing the Layout from Maximum to Minimum which can optimize performance but which would require adjustments of the Lasernet design.

Please ensure a backup is made of both the report-definition (Query) in Lasernet FO Connector and Lasernet design,  in case the conversion is not working as expected.

Converting from Maximum to Medium, Maximum to Minimum and from Medium to Minimum are currently supported but this will get extended in future releases.

Example

Follow these steps when changing output (XML file) from Maximum to Minimum

1. Ensure Update design is enabled – Lasernet > Setup > Parameters > Performance > TOOLS > Update design.

2. Make an export of the report definition (Query) in Lasernet FO Connector and the Form in Lasernet (it is possible to Export multiple forms from Lasernet and import them into Lasernet FO Connector).

3. Change the Layout for the Report from Maximum to Minimum within the Query Wizard. (SalesConfirmReplacement are (in this case) used as an example)

4. Run the report to identify patterns and rearranges that are not working as expected.

5. Import the Lasernet design into Lasernet FO Connector – Lasernet > Reports > Update design.

6. Select the required Form within the field Form in file  (required in case the file contains multiple designs).

7. Click OK to prepare a new Form which will get imported into Lasernet.

(This new Form/File contains the new patterns and re-arranges required for Lasernet Developer).

8. Import the file created in Lasernet FO Connector into Lasernet Developer (Design).

9. Use the following option to ensure the existing form is saved as a Backup.

10. Click Deploy/Patch.

11. Rerun the report and ensure the proper output is shown.

Review and Document Handling

Review of document(s) with "Review Before Sending" provides a great option to verify/approve document(s) before they are delivered. It’s possible to save the final document (normally a PDF file) as an attachment when making the delivery.

Using document handling in review will only work if archiving is activated and will not work for documents in which archiving is disabled, such as proforma documents. Save XML must be enabled.

The combination of review and saving the document as an attachment has been improved in Lasernet FO Connector 6.17 by adding a phase/status identifying the documents that haven't been delivered.

The note ['In review on report xxxx’] is added for the attachment in case the document hasn’t been delivered, such as when canceling the review.

The Pending review within the Archive would identify the document that has not been delivered.

Deliver report through the Review would ensure the Document is saved as an attachment (Document handling).

After the document is delivered through the Review.

Benchmarks

The following illustrates the benchmark/performance comparison between Lasernet FO Connector 6.16 and 6.17.

The Batch print schedule (Top picking) located in the Test & Performance Suite is used for all measurements.

Batch print schedule (Top picking) is extremely useful for end-customers as it provides the option to save benchmark/performance measurement over time – such as before and after upgrades of standard Dynamics or after an upgrade of an ISV solution – like Lasernet FO Connector.

Lasernet FO Connector 6.17 is generally much faster, especially when using many batch tasks/threads.

The following tables compare performance when using a different number of threads with Lasernet FO Connector 6.17:

The following tables illustrate a benchmark between using a subreport and a subreport converted into the Query.

Running 12 confirmation reports with 1000 lined each:

The following subreport was used for both subreport and for Query and was used at the line-level (CustConfirmTrans) for the report Sales confirmation:

Query Wizard - Examples

The following contains examples of the newly introduced features within the Query Wizard.

Top bar

Copy/Link Query

This provides the option to either copy or link to another Query.

Using a link to a Query provides the option to maintain and use one central Query – like a Query for the CompanyInfo. It's also possible to use a linked Query at detail/line levels containing information about item dimensions which could get re-used across multiple reports.

This is a similar approach to using a sub-report but would provide better performance as it would avoid round trips and initializing the report engine for the sub-report.

(Auto converting Subreport into Query)

The new feature Copy/Link Query provides the option either to copy another Query into the ’existing’ (current) Query or make a link (reference) to another Query.

It's also possible to convert existing subreport(s) into the Query by using the new feature Convert which is located within the structure (elements). Using Convert to a query link will convert the sub-report into the Query and leave the existing element containing the subreport as is but this should be set to invisible (Visible=0).

Sub-reports and Query links are accessible through the Query links located in Lasernet > Common > Reports.

Example

You could have a Query FPCompanyInfo containing the company information, such as the following example:

The Query FPCompanyInfo contains the following data sources/tables:

Follow these example steps:

1. Locate the Replacement Report/Query for which FPCompanyInfo should get used/linked.

The Report SalesPackingSlipReplacement and the FPCompanyInfo are linked to the data-source/table CustPackingSlipJour.

2. Open the Query Wizard, click the Copy/Link query in the step where the Tables are selected and choose which table the Query should get linked to.

3. Select or enter the Query name FPCompanyInfo in the field Source report.

Enabling Link (updates query on source change) would make a reference to the Query ( instead of just copying the Query) and would ensure the following options become available (the options below in bold):

A link to the Query FPCompanyInfo is now added to the Query –  the following 

The (Linked from FPCompanyInfo) identifies that it’s a link to a Query and not a copy.

Disabling Link (updates query on source change) would make a copy and not a link to the Query:

Auto conversion of sub-report into Query

Example

Imagine a Query that contains the following Company information:

This query is used as a subreport:

Lasernet FO Connector 6.17 contains a new feature that can convert the Sub-report into the Query. This would provide better performance especially if the Sub-report is used at the line/details level.

Ensure that all patterns/re-arranges are be used in Lasernet.

This is an example of converting Company information that is used at header/top-level:

Copy/Move

Provide the option to copy or move the datasource(s), plus the option to include all nested data sources.

This is useful when there is a need to re-structure data sources (tables) within an existing structure but also useful when there’s a need to insert a table between two existing tables.

Imagine there’s need for having the table SalesTable in between the tables CustConfirmJour and DlvMode.

It is possible to add the table SalesTable to the table CustConfirmJour. However, this would provide a structure in which tables are at the same level as the parent table which could cause issues in relation to joins and ranges.

A better approach is to have a nested structure and not have tables at the same level.

It is possible to move the table DlvMode by using the Copy/Move button.

You can use the Arrow up and Arrow down to adjust the order of the output.

Labels

Provide the option to add multiple labels within the Query Wizard.

It’s possible to add and see labels and Language texts at Data sources, Query, and at each datasource/table.

Load defaults provide the option to reload/add labels for one specific data source/table - the labels from all the fields which have been added for this specific data source/table:

Data sources

Properties when selecting Data sources

Parameters

Provide the option to include the parameters from either the SSRS/Replacement-report or from fields created through the Dialog setup within the Output (XML-file).

This is useful in case parameters for initializing the report get shown as part of the document, such as when there’s a requirement for showing  an account range, data-range which was used when running the Report.

It is best practice to provide the option to show which ranges have been used on top of a document, especially in the case of internal lists and documents. 

Enabling Parameters for a replacement report for SalesConfirm:

This will add a new section called Parameters which contains all the parameters which were used for initializing the report.

Output when enabling Parameters for a brand new Query report:

Language texts

Provide the option to include the language texts which has been added through the Report group. (this would automatically add the previously used method LACLanguageTextsReport().

Layout

Provide the option to specify what the file should contain (Min, Medium, Maximum). This is extremely useful when there’s a need to optimize performance, as it provides the option to lower the size of the XML file.

Maximum

Using Maximum will prepare an output including <Detail_Collection> and <Detail>.

Medium

Using Medium will prepare an output including <Detail> but not the <Detail_Collection> .

Minimum

Using Minimum will prepare an output only containing the data-source name and without both <Detail_Collection> and <Detail>.

Labels

Provide the option for adding multiple labels and language texts for a specific Query.

All labels or language texts added for a specific Query or data-source are also shown at the Data sources (top level).

Query

Properties when selecting a Query

Create element

Option to specify if the Query name should get added to the XML file.

Create element is automatically enabled when converting a sub-report into the Query structure as this would ensure the same structure as when the sub-report was used.

Having a structure such as the following image in which DlvMode only is required for finding the translation (LanguageTxt) but isn’t required within the output (XML file).

It’s possible in Lasernet FO Connector 6.17 to avoid a data source (table) being created by setting Create element to No.

The following example illustrates an example in which the table DlvMode isn’t required for the output (XML file) as only the translation (LanguageTxt) is required.

Avoiding tables in the output would both make the Output (XML file) more readable and would also create a better performance as this would lower the size of the output (XML file) as the content would get lowered.

DlvMode would as ’default’ be added into the output (XML file).

It’s also possible to avoid a data source being added by setting Create element = No, which will avoid the data source (table) being added as part of the output (XML file).

Output without having DlvMode.

It is still possible to use the table in relation to other tables and within an expression.

Show labels on

This option enables users to specify where and how often labels should get shown within the XML file.

Normally a label is only required once within a document and having a lot of repeating labels could harm performance. Show labels on has been introduced to avoid repeating labels.

EachDataSourceNode

FirstDataSourceNode

Using the FirstDataSourceNode would only add a label once for each data source.

The following example illustrates the differences between EachDataSourceNode and FirstDataSourceNode.

EachDataSourceNode	FirstDataSourceNode

The following Query was used for the illustration above:

Hide

No labels are shown. It is possible to specify the label behavior at both Query and each data source.

Top 

Labels and language texts are always shown at top of the XML file and within the section <Labels>.

Having labels at top of the document and avoiding repeating labels can both optimize performance and also be useful in case of a situation in which label(s) always need to be shown.

The following example demonstrates when the label for the Bar code always should get shown even when no barcode exists:

Using Top in Show labels on would ensure labels always are added to the output (XML file).

The LABEL_Bar_code would will always get shown as Show labels on is set to Top.

Show labels on is set to Top to ensure labels always are added.

Labels

Provide the option for adding multiple labels and language texts for a specific Query. Labels or language texts are added for a specific Query.

All labels/language texts added for data sources are shown at Query and at top level.

Bug Fixes and Enhancements

Create a simple Install/Upgrade framework

(283787@LAC365FO – Create a simple Install/Upgrade framework to handle tasks that are normally part of the customer documentation) 

A new framework is introduced for managing tasks that are related to the upgrade of Lasernet FO Connector.

This should automatically get executed. It is also possible to manually start from the location Lasernet > Setup > Parameters > Install / Upgrade tasks > Run Lasernet Install/Upgrade tasks.

Culture info adjustment in LAC setup parameters

(291857@LAC365FO - Culture info adjustment in LAC setup parameters does not get transferred to other entities when exporting or copying)

The choice to export the Culture info adjustment is added as an option in Lasernet FO Connector 6.17.

Adding a” Yellow element” would cause an empty output and using the values from the TMP-table as a range for the sub-report could cause a long-running report (Query), as it would fetch all the records in the sub-report as no ranges were passed.

This is fixed in Lasernet FO Connector 6.17.0.

Subreport not working in LAC 6.16

(280604@LAC365FO - Subreport not working in Lasernet FO Connector 6.16)

Replacing an SSRS-report using TempDB for the tmp-table(s) could cause empty values to get returned when adding a field within the structure/elements such as the Report:

ReturnAcknowledgmentAndDocument

The issue was only related to Lasernet FO Connector 6.16 and only occurred in some specific scenarios using TempDB.

Object reference not set to an instance of an object when printing 

(277620@LAC365FO - Object reference not set to an instance of an object when printing to LN printers)

Using a condition for the Lasernet server could cause the following error message:

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

This is now fixed.

Reports generated by Alert links are marked as being a copy

(277518@LAC365FO - Reports generated by Alert links are marked as being a copy)

Reports started through an Alert link were marked as copies within the Archive.

Entries within the Archive triggered through an Alert link are no longer marked as a copy in Lasernet FO Connector 6.17. 

Load defaults for email subject and body

(272246@LAC365FO - Load defaults for email subject and body are not loaded in printer settings, default report in printer settings)

Printer settings and Load defaults would always use the ”original” SalesInvoice.Report (SalesInvoiceReplacement) and not the report specified within the print management for the report:

Lasernet FO Connector 6.17 contains a new option that would use the report specified within the print management for the printer settings and this for the Load defaults as well.

This would ensure printer settings (incl. Email subject/body) are found from the report specified within the print management.

Bug - Alert link report processing

(274226@LAC365FO - Bug - Alert link report processing)

An issue with alert links and when using cross-company data sharing has been fixed.

Change Selection tables to class name instead of ID

(199837@LAC365FO - Change Selection tables to class name instead of ID.)

The Default for the backup (Export) is changed and is using the class names instead of the ID.

Please run Register selection-classes which is located in Lasernet > Backup parameters > Setup Default Selections in case of the following error:

'Export of Lasernet backupPlease try to run 'Register selection-classes' before proceeding.'

Automatic back up of the LAC365FO configuration

(191709@LAC365FO - Automatic back up of the LAC365FO configuration)

The Export (Backup) now includes the option to run the Export within a batch task. This provides the option to have a nightly backup. It also provides the option to automatically move between environments as it’s possible to configure a static file name and use the existing Connection type/connections such as Azure, File-system, etc.

Both the Export and Import provide the option to run in a batch.

The new option Endpoint type is added when making an export. Selecting Lasernet Connection provides the option for selecting the existing connection for the Storage, such as Azure Storage, File-system, etc.

Warning if Lasernet-archive is included in the export/import

(156447@LAC365FO - Warning if Lasernet-archive is included in the export/import)

The following warning is thrown if the Lasernet archive is included in the selection of the Backup or included through the Predefined selection:

'Including 'Lasernet Log' can significantly increase the processing time and backup size.'

'Export of Lasernet backupPlease try to run 'Register selection-classes' before proceeding.'

Bug Fixes and Enhancements – LAC365FO Version 6.17