Release version: 6.20

Release date: 11th March 2024

Introduction

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

Click to view the Lasernet FO Connector 6.20 Release Notes.

Click to view the Models and Prerequisites page.

Video Overview

Watch this short video to learn more about the headline features included with Lasernet FO Connector 6.20!

New Features and Major Enhancements - Lasernet FO Connector 6.20

Focus:

• Quality

• Reliability

• Flexibility

Lasernet FO Connector 6.20 is released for Dynamics 365 for Finance and Operations versions 10.0.36 (PU60), 10.0.37 (PU61), 10.0.38 (PU62), and 10.0.39 (PU63).

The same code is used across all versions.

This is aimed to be a quality update, provided through these new features and enhancements:

• Improved options to specify/lock a destination, including in Query reports.

• Improvement on Default printers when using the Microsoft ® Warehouse Management App.

392910@LAC365FO - Option to specify/lock a destination, including in Query reports

In previous versions of Lasernet FO Connector, it was only possible to specify/lock a destination when working with SSRS reports.

Specifying a destination for an SSRS report is extremely useful, especially when the SSRS report is only using Print management, and if there is no option to specify a destination for the report.

A good example would be a WHSLoadList report, which always uses the setting from Print management. Printing a Load list report from the form would, therefore, always use the destination specified within Print management for the report.

In previous versions, it was possible to specify a destination through the Dialog options field located at the report level (General > Dialog options).

The Dialog options for the report would enable a printer dialog even though the SSRS report only reflects settings from Print management when printing from the form.

Previous version – Dialog options

With Lasernet FO Connector 6.20, it is also possible to specify/lock a destination for a newly created Query report.

The Dialog options field has been moved from the General to the Destination defaults fast tab and is now named Printer settings initialization.

Both Start with and Specified (read only) are useful if a business wishes to ensure that the end-user can always select a proper destination, such as a predefined destination.

Using Start with allows the destination to be changed when resending from the Journal or the Lasernet Archive, whereas Specified (read only) always uses the destination specified for the report with no option to adjust the settings.

It is, however, possible to specify whether Force rerun should be used or not when resending from the Journal or the Lasernet Archive.

Using Specified (read only) will show all destination types but will only allow the user to choose the destination type previously selected with Specified (read only). Selecting a destination type different than the one set in Specified (read only) will trigger the UI to fall back to the one selected within Specified (read only).

It is possible to use Print buttons, but this option is not relevant when using Specified (read only) as this has the highest relevance and would not enable the print buttons to overwrite the destination.

All print buttons will be disabled if Specified (read only) is used. For instance, in the following image, Specified (read only) is used for the Confirmation report.

Print to (presets) is an extremely powerful feature as it provides the option to filter which printers or destinations should be shown to a user.

It is also possible to specify the printers/destinations for each report/Query for all users, a group of users, and a specific user.

The destinations can also be shown as a button. However, there are often not enough printers/destinations for a report; therefore, it is preferable to show the primary printers/destinations as buttons and the secondary printers/destinations as a list in the Print to field.

In Lasernet FO Connector 6.20, Print to (presets) reflects the destination specified for the report. The following image demonstrates this, where Start with and Fax Initialized destination are specified for the report:

Lasernet Fax - Initialized destination will, therefore, be shown in the Print to (presets).

A Lasernet destination will always be shown if a report is configured for Lasernet. However, it is possible to change to a standard destination for SSRS reports unless it is read only.

If, after the execution of an SSRS report, the user converts the report to Lasernet, they will also need to manually set an SSRS destination (if needed).

The Printer settings initialization must be configured for the replacement report if the SSRS report is replaced with a Query.

Try to enable or disable one of the following report-related fixes if a printer dialog is not working as expected:

It is not possible to print a document from a preview if the destination for the report is set to Lasernet screen. For instance, the following report is set to Fixed (read only)

and the destination is locked (read only) to Lasernet Screen.

The Print button is showing in the Preview. It is not possible to change the destination as it is locked (read only).

The destination is fixed to Lasernet Screen and will, therefore, always go back to Lasernet Screen even when trying to select another destination type.

A similar process occurs during the review if Fixed (read only) is used.

Use the Start with option if you need to change an already selected destination when re-sending from the report level or the Lasernet Archive.

392080@LAC365FO - Default printer(s) when using Warehouse Management app

The option to define a default printer has been improved within the Warehouse Management app, including a new option to define a list of printers that should be available for the mobile user when using the Warehouse Management app.

In addition to this, it is now also possible to scan and set a default printer directly in the Warehouse Management app.

The following sections will guide the user through the configuration phase, usage (with multiple scenarios), and functionalities of this new feature.

Configuration

1. Navigate to Warehouse management > Setup > Mobile device > Mobile device Menu items.

2. Click New to create a new menu item, then give it a name and description.

3. Choose the Override label Lasernet Printer option in the Activity code field.

4. Navigate to Warehouse management > Setup > Mobile device > Warehouse app field names.

5. Configure Lasernet printer name to Scanning to approve scanning.

6. Add your newly created Mobile device item to the mobile device.

How to Use it

1. Open the Warehouse mobile device and navigate to the menu item Override Lasernet label printer.

Here, you have the option to scan or write the name of the printer with which you wish to override the default printer.

The printers you can view can override the default label printer.

This list reflects the options available at Lasernet > Setup > Defaults > Default printers.

To learn more about these topics, visit the following links:

• https://support.formpipe.com/guides/lasernet-fo-connector-user-guide/lasernet-fo-connector/defaults/default-printers-2

• https://support.formpipe.com/guides/lasernet-fo-connector-user-guide/lasernet-fo-connector/further-resources/create-mobile-device-labels-lacwhsprintlabels/mobile-device-app-print-number-of-copies-and-specific-layout

• https://support.formpipe.com/guides/lasernet-fo-connector-user-guide/lasernet-fo-connector/further-resources/create-mobile-device-labels-lacwhsprintlabels#default_printer_references

What to Expect from Available Printers

Users can only use printers made available to them to override the default printer.

Scenario 1:

This printer is only available to the Sales report group. Therefore, it is not available to select on the mobile device.

Scenario 2:

This mobile device test user is working on Site 2, Warehouse 24. This printer is, therefore, available to select on their mobile device Lasernet Override label printer.

Scenario 3:

This mobile device test user (User ID 24) is working on Site 2, Warehouse 24. This printer is, therefore, not available to select on their mobile device Lasernet Override label printer.

Scenario 4:

This mobile device test user (User ID 24) is working on Site 2, Warehouse 24, but is not on Location 3000. The printer is, therefore, not available to select on their mobile device Lasernet Override label printer.

View and Update the Worker in Dynamics

For transparency purposes, it is also possible to view and update a worker’s feature in Microsoft ® Dynamics.

Navigate to Warehouse management > Setup > Worker: a new field - Label LASERNET Printer - has been added to show the worker’s default Lasernet label printer.

To change or remove a printer for a specific worker, follow these steps:

1. Select the worker and click Override label LASERNET printer.

2. Use the Printer dropdown to choose the printer. The list of printers is the same as found in Lasernet > Setup > Printers.

3. Click OK.

The printer that will be used by the worker has now been updated.

Bug fixes – Lasernet FO Connector version 6.20

408460@LAC365FO - Issue in 10.0.39 - A container for table (xxx) was packed with more fields than are currently defined on the table

Once you upgrade to Finance and Operations 10.0.39 (PU63), you might encounter an error message such as the following:

This happens when performing one of these three actions:

• Resending from the Lasernet Archive with force rerun.

  The solution for this scenario is to run the Optimize Lasernet log job in Lasernet FO Connector 6.20 before upgrading Dynamics 365 FO to 10.0.39 (PU63).

  The only downside when Lasernet FO Connector 6.20 is installed after upgrading Dynamics 365 FO to 10.0.39 (PU63), is that Resend with force rerun will not work from the Lasernet Archive.

  Resend without force rerun will, instead, still work, and Resend from the standard journals will work as well.

• Navigating through the records in the Lasernet Archive.

• Exporting records with entries from the Lasernet Archive.

  It is not necessary to install Lasernet FO Connector 6.20 before updating Dynamics 365 FO.

This example shows the error message for a Packing Slip, and it uses the table CustPackingSlipJour. This table is just an example, and the error could apply to any other table.

However, this all depends on the previous configuration of Dynamics 365 Finance and Operations 10.0.39 (PU63).

Questions and Answers

• How do I ensure that Resend with force rerun is working as expected when resending from the Lasernet Archive?

  You must install Lasernet FO Connector 6.20 before you update Dynmics 365 FO to 10.0.39 (PU63).

  You will also need to run Optimize Lasernet log as this will adjust the records required for Resend with force rerun within the Lasernet Archive. The option Force rerun when resending a document from the Lasernet Archive is used when re-executing or initializing a report from scratch.

• What happens if I install Lasernet FO Connector 6.20 after I upgrade Dynamics 365 FO to 10.0.39 (PU63)?

  You cannot use Resend with force rerun from the Lasernet Archive. Using Resend without force rerun from the Lasernet Archive will work as expected, and Resend will still work when used from the standard journals as well.

  No error messages will be thrown when:

  1. Using Resend from the Lasernet Archive, with or without Force rerun.

  2. Navigating through the records within the Lasernet Archive.

  3. Exporting records from Lasernet and the Test & Performance Suite.

• What happens if I do not install Lasernet FO Connector 6.20 after the upgrade to Dynamics 365 FO 10.0.39 (PU63)?

  The Resend feature in the Lasernet Archive might not work, and the error message will appear. This can happen whether you use Resend with or without the option to Force rerun.

  Sending from the regular journals will function as usual.

  The error message can be thrown when:

  1. Using Resend from the Lasernet Archive, with or without Force rerun.

  2. Navigating through the records within the Lasernet Archive.

  3. Exporting records from Lasernet and the Test & Performance Suite (checkpoints).

• What about checkpoints that have already been created within the Test & Performance Suite?

  Running checkpoints will function in Dynamics 365 FO 10.0.39 (PU63) with or without Lasernet FO Connector 6.20. When exporting the checkpoints, an error message might appear, but the necessary data is correctly exported.

Task ‘Optimize Lasernet Log’

In Lasernet FO Connector 6.20, the function MINIMIZE RE-PROCESSING DATA (LACARCHIVERESENDDATA) has undergone some changes to ensure records are saved in a way that allows the use of Resend with force rerun even if the structure of the tables changes over time.

The data needed to use Resend in the Lasernet Archive has been improved, and it does not need a full and fixed record that depends on a table (such as CustPackingSlip or CustInvoiceJour). The necessary information is obtained at runtime.

You only need to run the task SHRINK RE-PROCESSING DATA (LACARCHIVERESENDDATA) once, because any new records created in Lasernet FO Connector 6.20 will be the same as those created through SHRINK.

You can start the task either from the Lasernet Archive (Lasernet > Common > Reports > Journal) or from the Lasernet parameters page ( Lasernet > Setup > Parameters).

Keep in mind that the ranges will use the current record if the task is launched from the Lasernet Archive.

It is advisable to run the task one report at a time if the Lasernet Archive contains several entries.

Optimize Lasernet log

• From the Lasernet Archive (Lasernet > Common > Reports > Journal):

• From the Lasernet parameters page ( Lasernet > Setup > Parameters):

The SHRINK option will enhance the way data is kept:

This is what Lasernet FO Connector 6.20 will show when it encounters illegal records in the Lasernet Archive. This, however, will only affect the use of Resend with force rerun from the Lasernet Archive once Lasernet FO Connector 6.20 is installed/deployed:

If an error message is displayed, a Tool icon appears next to the Resend data size field. This Tool icon provides the option to remove invalid records/unauthorized information.

Only the information required for Force rerun is deleted, while the entries containing the documents (XMLs and PDFs) are preserved.

When the Tool icon is clicked, a prompt such as the following appears:

It is possible to delete the following Usage data in case the Yes to all prompt is selected, and if the same prompt will be re-applied when resending documents from the Lasernet Archive.

The following message is displayed when attempting to resend the documents from the Lasernet Archive if they contain illegal/unlawful information/records:

Remove Invalid Records (Optimize Lasernet Log)

Lasernet FO Connector 6.20 allows the deletion of unlawful records from the Lasernet Archive. This is comparable to the use of the Tool icon that appears next to the field Resend data size.

Only the information required for Force rerun is deleted, while the entries containing the documents (XMLs and PDFs) are preserved.

Over time, Lasernet FO Connector 6.20 will either disregard or fix the error message.

The Only resend data with packed invalid records option is only available in case the DELETE RE-PROCESSING DATA (LACARCHIVERESENDDATA) option is selected.

The size of the records is reduced both when running SHRINK RE-PROCESSING DATA (LACARCHIVERESENDDATA) and when new entries are created within the Lasernet Archive (from Lasernet FO Connector 6.20).

In the following example, the report Sales Invoice that needs to be resent with Force rerun has been reduced in size from 13.1 to 8.6 KB.

Force rerun when resending documents

Documents are usually resent from either the standard journals or the Lasernet Archive without Force rerun since this second option will use the existing document.

Usually, consultants use Resend with force rerun from the Lasernet Archive because it speeds up the process and they may be unaware of the process’s starting point.

For most companies and end users, it is enough to either Resend from the standard journals or Resend without force rerun from the Lasernet Archive.

To enable the use of Resend with force rerun, information is needed, which takes up some extra storage.

One way to prevent the need for extra storage is to not choose On archive or On forms and Archive in the field Allow forced rerun. As a result, there will be no option to use Force rerun from the Lasernet Archive.

405017@LAC365FO – Odata subreport filters disappearing after importing

If a report/Query linked to a subreport using OData (Dataverse) as origin/source was exported, it would remove any added ranges (filters) within the main report/Query.

For example, the subreport in the following image uses OData (Dataverse) as source/origin.

The SubReport:LACOData uses OData (Dataverse) as the origin for the data source/entity within the Lasernet FO Connector.

Exporting and re-importing the report/Query would remove any added ranges or filters for the subreport.

Lasernet FO Connector 6.20 ensures the ranges and filters are kept in place.

404797@LAC365FO – XML structure issue LAC v6.19

An additional Detail could be created within the Output (XML file) if a child data source was an Extends feature of the parent table, as well as if no records existed for the child data source.

For example, in the following image, the DirPerson table is a child data source of the DirPartyTable table:

The DirPerson table Extends the DirPartyTable table.

Records exist within the DirPartyTable table.

However, no records exist with the same RecId in the DirPerson table. Therefore, there should be no output for the DirPerson table, as the RecId field is used as a relation between the two tables.

404347@LAC365FO – Missing data in XML when using group by in Query wizard

Using multi-tables for a Group by Query could cause empty records to show up in the child tables/data sources.

For instance, in a Group by Query using the SalesTable and CustTable table, the InvoiceAccount field from the Sales order (SalesTable), and the Blocked field from the CustTable table for the grouping.

Not all records would be properly grouped in the child data source.

404332@LAC365FO – Maximum read depth error when importing uncompressed Lasernet backup

The following error could be thrown when importing a sizeable backup file (XML file):

The maximum size has been adjusted.

402496@LAC365FO – Validation cut short due to infolog.clear without parameter

The Infolog shown when validating a report/Query was sometimes cut off.

This is now fixed.

402401@LAC365FO – Expression editor with long expressions is not catching up with text typed, and showing lookup but not updating text recognition colors

An issue arose with the Search functionality when changing/typing an extensive expression within the Expression editor, such as the following:

IF Calculated.DataContract().parmPrintDestinationSettings().printMediumType():NAME <> SRSPrintMediumType::LACScreen:NAME

then FalseTrue::True

else FalseTrue::False

Everything would work as expected. However, there would be an issue with the lookups: brackets for the DataContract() would be removed and would require to be added again before the selection would work as expected.

Adding expression:

Re-entering expression – () removed:

402512@LAC365FO – CustConfirmTrans.SalesLine().enum return wrong value

The wrong Enum type was returned when using a field from a record method.

In the following image, for instance, the Blocked field is selected from the CustTable table (custTable_CustAccount):

In a previous version of Lasernet FO Connector, Reservation appeared in the XML Output instead of No.

Lasernet FO Connector 6.20 returns the proper datatype.

402272@LAC365FO – Expression Editor - Fields with :NAME or :LABEL affixes are not recognized in switch statements

The use of :Name or :Label as an Enum would not be properly recognized within the Expression editor when used for a Switch statement.

Using :Name would return the system name for the label, whereas using :Label would return the translation for the label compliant with the language used in the report.

Report language da is used in the following example:

In a previous version of Lasernet FO Connector, CustTable.Blocked:Name and CustTable.Blocked:Label would return the following values when da was used as the report language:

This is fixed in Lasernet FO Connector 6.20, which supports the use of :Name and :Label within a Switch statement.

Switch CustTable.Blocked:Name

Case "Yes" Then "Checked"

Case "No" Then "Unchecked"

End

401239@LAC365FO – LAC 6.19.1: Issue with SharePoint attachments with duplicate original file name

The JobInfo MailAttachmentFileStorage now contains the File name instead of the Original file name used in previous versions.

This provides the option to give files unique names if, for instance, the same attachments are added multiple times.

400011@LAC365FO – Subreport Range with Quotes not supported in Lasernet FO Connector version 6.19.1

400931@LAC365FO - Subreports Filter ranges with Custom fields Ignores "Skip" If Ranges are Empty

The use of quotation marks (“) within a value Range in a subreport was not respected, and the whole record was created as part of the output for the subreport as the Ranges were ignored.

For example, in the following images, quotation marks are used for the hardcoded value DE-001 – “DE-001”:

A similar issue arose if the option to Skip execution of the subreport was used, and the Range field was left empty. All records would be included, and the Ranges would not be accepted if quotation marks were used.

This is now fixed.

400661@LAC365FO – Manual changed output names and types are changed after import

Using the option to Refresh stylesheet after an import could cause manually changed output names to be reverted to their original names.

In the following image, ISO was added as a postfix for the Output:

This could also happen after an import unless Update stylesheet were disabled.

In this case, ISO would be removed, and the Output would be reverted to the original name. The Type would, therefore, be reverted to the related/original type/datatype (Real in this example).

This issue is now fixed.

400651@LAC365FO – Document handling missing if report is run from code in batch and LACRunQueryServiceController::newReport parameter loadLastValue is false

The following code would not properly create the report in Document handling if running within a batch task, and when the argument loadLastValue was set to False.

The code would only work when not running within a batch task or when setting loadLastValue to True.

LACRunQueryServiceController controller =

LACRunQueryServiceController::newReport("WI_400651_Missing_DocumentHandling",

LACArgsCache::newCache('WI_400651_Missing_DocumentHandling'),false);

The following is the setup of Document handling for the report executed through this code:

At this point, a document should be created and attached in Document handling for the customer. However, no record was created in the previous version of Lasernet FO Connector: the Documents section would be empty in the XML file.

This is now fixed.

400636@LAC365FO – Unable to access Cash Flow Forecast workspace

The following error was thrown when trying to access the workspace Cash flow forecast:

This is now fixed.

400293@LAC365FO – Direct SQL queries execution builds different structure to AX query execution

Adding a Direct SQL to a Group by Query would change the output structure. Such as when adding the RowNumber to a Group by Query.

RowNumber is a useful tool when working with variants, such as models/brands, sizes, and colors within Retail.

The following Group by Query groups SalesId and Salesname from the salesTable table/data source, and SalesId and ItemId from the SalesLine table/data source:

Adding RowNumber would change the structure of the output (XML file).

402008@LAC365FO – Unable to run report when layout set to “Same level as parent” and fetch mode set to 1:n

The following error could be thrown when running a report/Query, especially if the Query used SameLevel (same level as the parent) for the Layout, and One2Many (1:n) for the Fetch:

This is now fixed.

399910@LAC365FO – Issue to use an Array ([1], [2]) within the Expression editor

It was not possible to use an Array field as part of an Expression within the Expression editor.

Using FilterCode[x] would throw the following warning:

399225@LAC365FO – QW: Duplicate found error if adding same table more that once

Adding the same tables multiple times with the same fields/methods throws the following errors when finishing the Query wizard.

This only happens when the same fields and tables are added multiple times and at the same time.

A workaround is possible, which is not to add the same fields and tables simultaneously within the Query wizard.

It is also best practice not to add the same information/fields multiple times within the Query wizard.

399917@LAC365FO – Custom query serializer

399210@LAC365FO – Exception has been thrown by the target of an invocation. Invalid replacement key ID for table '{0}'.

Lasernet FO Connector 6.19 and 6.19.1 use serialization and de-serialization when using Export, Import, or Copy on reports across companies/legal entities.

These rely on the metadata service in standard Dynamics 365, which could cause issues in relation to views, table groups, and display methods.

Lasernet FO Connector 6.20 contains an improved metadata service to ensure Export, Import, and Copy work as expected.

Examples of issues:

Views

The following errors are thrown if the report/Query contains the view InventDistinctProductExpanded.

• When using Import:

• When using Export:

• When using Copy to another company/legal entity:

Code – Legacy approach which can cause issues:

public static final class CustGroup_Legacy_Extension

{

public static display Description descriptionLegacy(CustTable record)

{

return "Legacy display method for CustGroup";

}

}

Code – Regular approach which would work as expected:

ExtensionOf(tableStr(CustGroup))]

public final class CustGroup_Regular_Extension

{

public display Description descriptionRegular()

{

return "Regular display method for CustGroup";

}

}

Display Method

The following error was thrown if a display method such as the following was added, even though the display method was not added as part of the report/Query:

[ExtensionOf(tableStr(CustGroup))]

public final class CustGroup_Regular_Extension

{

public display CustTable descriptionRegular()

{

return CustTable::find("US-001");

}

}

• When using Import:

• When using Export:

• When using Copy to another company/legal entity:

399541@LAC365FO – ProdRouteCard always generate one report without ProdTable data and one correct report

Group data in files allows files to be split into smaller parts based on the existing fields already used for the Query.

This feature is similar to Group by. However, Group data in files will not group the data within the same file but will create multiple files based on the added fields.

It also ensures that communication between the XML file and the generated output from Lasernet works properly. For instance, if multiple files need to be shown as Preview within Lasernet FO Connector.

An additional record and associated file used to be created in previous versions of the Connector. With Lasernet FO Connector 6.20 this will not be possible.

399069@LAC365FO – Email body editor images on Destinations are not working as expected

When working with images within the Email/HTML editor, the user could view an incorrect dialog for Image Properties.

This has been fixed.

The Image Properties settings have also undergone some changes.

395879@LAC365FO – Change label from 'Lasernet plugin' to 'Lasernet FO Connector'

Lasernet FO Connector was previously known as LAC365FO. This naming convention has changed.

The new naming convention for the Lasernet FO Connector has been applied to the Lasernet parameters page:

395052@LAC365FO - Default Printer selection doesn't allow 'Review before sending'

In previous versions of Lasernet FO Connector, it was not possible to use a default printer for Review before sending.

This has now been fixed.

394125@LAC365FO – Object Reference Error in DM FO Connector When Showing 10+ Keys

When adding more than ten keys for the mapping between Lasernet FO Connector and Autoform DM, the following error was thrown:

The maximum number of keys from DM that could be used for mapping the fields between DM and the FO were:

• nine String fields

• two Date fields

• two Real fields

Refreshing the forms in which the buttons for Autoform DM were added (configured through the Form links for Autoform DM) required, at times, to refresh the form in the following image:

The following warning is shown in Lasernet FO Connector 6.20 if the maximum number of fields is reached when either entering the fields or fetching the data from Autoform DM.