Lasernet FO Connector 6.19 New Features and Fixes

Lasernet Connector for Dynamics 365 Finance and Operations

Release version: 6.19

Release date: 17th October 2023

Introduction

This page describes the new features, fixes, and enhancements in Lasernet FO Connector 6.19.

Click to view the Lasernet FO Connector 6.19 Release Notes.

Video Overview

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

Major Enhancements - Lasernet FO Connector 6.19

Focus:

• Quality

• Reliability

• Stability

• Performance

• Flexibility

The main focus is still on Quality, Reliability, and Stability, but some enhancements have been made to support Flexibility and Performance.

One major adjustment in Lasernet FO Connector 6.19 is serialization: this is essential for the version control (DevOps) planned for a future version of Lasernet FO Connector.

Important are also the improvements made within the Test & Performance Suite, including features that can assist in automating the testing process.

Automation of the testing process is important as this can assist in ensuring a smooth upgrade.

Lasernet FO Connector 6.19 includes the following major enhancements/features:

• “What’s used” analysis

• “Compare PDF files” (useful with upgrades)

• Improved Update of Lasernet design within Lasernet FO Connector

• Built-in storage explorer

• New option to parse attachment(s), especially useful with SharePoint

• Improved review/preview of documents including alternative destinations within Review

• Option for unique archiving even when having multiple designs linked to the same Journal

• Improvements in the Test & Performance Suite

  • Report playback/destination

  • Option to Ignore usage data (last values)

  • Use contents (XPath) in XML-file for validation

  • Re-recording of existing recording(s)

The features What’s used and the option to Update Lasernet design within Lasernet FO Connector are extremely useful: the former provides the option to identify which tables and fields are used, while the latter allows to “auto-adjust” an existing design.

What’s Used

We have created this function because, until now, Consultants would need two screens to compare the Lasernet Connector and the Lasernet Developer, and validate which fields are used and which can be deleted.

What’s used enables users to import a design (Form) from Lasernet (.lnobject, .lnobjectx) into Lasernet FO Connector.

Now, once the design is imported from Lasernet, the Lasernet Connector for Dynamics 365 Finance and Operations can show which tables (patterns) and fields (re-arranges) are being used within the Form in Lasernet.

Green - Shows which data sources/tables are used in Lasernet

Red - Shows unused data sources/tables

Similarly, concerning the used fields:

Unused tables (patterns) and unused fields (re-arranges) might have either been previously added for debugging purposes or been there due to new or changed business requirements.

Having only the fields that are effectively used within the Lasernet Connector Query can increase performance and handover satisfaction between the Delivery/Implementation team and the Support team.

Read more in the What’s used (Example) section.

Compare PDF Files

This version contains a powerful option for comparing PDF files.

This is useful when the user needs to validate whether the final document output (PDF file) matches the output before the upgrade.

The idea is to save checkpoints containing the XML/PDF files before an upgrade and use the same checkpoint after upgrading to compare the files.

Read more in the section Test & Performance Suite.

Browse files within Azure Storage

It is now possible to browse files from different storage types, the same storage types that can be used to save the XML file used for the communication between Lasernet FO Connector and Lasernet (File, Azure Storage, and Sharepoint).

Location: Lasernet > Setup > Administration > Connections > Browse.

Clicking the Browse button opens a file explorer with the standard “file management” features:

The file path is clickable, so you can use it to navigate back through the directory structure.

The home button allows you to return to the root directory of the file system quickly and easily.

Filtering/Search

The search feature presents two points of interest: a search filter and a condition-based search. Through the search filter, it is possible to filter files based on their names. Through the condition-based search/filter, it is possible to set up conditions for the search.

Change to “Perform operation”

The button previously known as Perform operation has now been renamed Action and moved inside the new Browse feature.

Import/Export report backup

The update also includes the Import/Export of report backups.

Location: Lasernet > Common > Reports > (Import report backup / Export report backup).

In this example, we will describe a scenario where the Import report backup is used.

Upon importing a report, the Endpoint type should be set to Lasernet connection for the new feature to be visible. To find a report, the Connection should be the storage that contains the report. This allows to explore the storage, find the intended report and import it.

After the file has been found, it is possible to click Open as shown in the following image:

Once the file has been opened, the name of the file will appear inside the Filename field. When all the information is correct, click the OK button to finalize the import.

Toggling the Dynamic button to Yes allows getting to the next step without reading the file.

This provides the option to configure the batch schedule without needing to add the file, as the system would otherwise not allow proceeding to the next step.

Storage Explorer

This version contains a storage explorer that can show the content of the storage types used for the integration between Lasernet FO Connector and Lasernet, such as File system, Azure, and SharePoint.

This is useful when the user needs to debug/check whether the XML file has been created and whether it looks ok. It can also be useful when checking the outcome from Lasernet, such as whether both the PDF and EDI/OIO files have been properly created.

It is possible to both upload and download through the storage explorer, which is also useful when needing to share information.

This can also be used to move file(s) between environments, such as when XML files need to be within a UAT environment for which only the records (DB) are restored from PROD.

Auto-update of Lasernet design

The option to auto-update a Lasernet design was introduced in Lasernet FO Connector 6.17 and has been significantly improved.

In previous versions of Lasernet FO Connector it was only possible to auto-adjust a design in case the layout dimensions were lowered (a layout would have to go from Maximum to Medium, from Medium to Minimum, or from Maximum to Minimum).

The layout specifies the level of context added to the XML file, such as whether Detail Collection and Details should be added or not.

This version can also auto-adjust a design when its dimensions are increased (the layout goes from Minimum to Medium, from Medium to Maximum, or from Minimum to Maximum).

Lowering the layout means creating smaller files, whereas increasing the Layout means creating lager files (XML files).

Using a maximum layout means having larger XML file(s), which, in some situations, can be useful as it provides the option to “collect” (expand/collapse) the data and could, therefore, provide an easier and more readable document within the Lasernet designer.

Update design provides the option to keep the history of the modifications made to the layout over time.

These historical modifications are shown in the form called Designs.

This form is created as a historical overview of designs.

The following picture shows two designs that we imported from Lasernet. They get the Description “Imported design”.

The report named “Version3” has been created by clicking Update design > Create new design version. This saves the new version with the description “Updated design in D365 Design updated”.

In a future version of Lasernet FO Connector, it will be possible to check-in/check-out the version to TFS (DevOps).

The form now also contains information about the Input object and Output object used in Lasernet, which is often quite useful, especially when working with calculations across patterns in Lasernet, as it is through this form that it is possible to search across all the patterns.

Update design is also useful in case the user is updating an older version of Dynamics where Lasernet was already used (such as upgrading AX2009, AX2012 into Dynamics 365): this is achieved by exporting the existing design and importing it into Lasernet FO Connector.

The field Lookup provides the option to remap fields if there are new fields or the existing re-arrange has changed.

The auto-update function also provides the option to adjust a Lasernet design in case the structure (Output) is changed in Lasernet FO Connector.

Read more in the Update design (Example) section.

Review/Preview of documents

This version supports the following three file types being displayed within the same document preview form:

• Document file (normally a PDF file)

• Custom file (EDI, XML/OIOXML, CSV, EXCEL, Word etc.)

• XML/Grab file

A similar approach is used when previewing original documents from the journals in Lasernet FO Connector.

It is possible to toggle between the document (PDF), Custom document and XML file.

Alternative destination when reviewing a document

Reviewing a document provides the option to approve the document before it is delivered. This also provides the option to hold back a document, such as an attachment that needs to be added before the document is delivered (CRM / Bill of lading etc.).

In previous versions of Lasernet FO Connector, it was not possible to change/alter the destination when reviewing a document.

This version provides the option to change/alter the destination when reviewing a document.

This example shows the option to make a print-out of a document before it is distributed. Sometimes a print-out provides a much cleaner/clear view of the document.

Document review can also be useful for validating the destination(s) found through the pre-defined destinations (rules for destination), such as a TEST, UAT environment where the delivery is required.

New options for attachments

This version provides the following four options to add an attachment: URL, Base64 file, URL XML, URL original. All options work well with review of documents, where it is also possible to add additional attachments.

These are especially useful for attachments coming from SharePoint as they give the option to parse the attachments through either an alternative Storage or by using a URL linked to the original location of the attachments.

"Graph" is used as a prerequisite for SharePoint in both Lasernet and within our Lasernet FO Connector . However, it is possible to use legacy, although this requires a specific connection (the internal connection-id in Dynamics 365 Finance and Operations).

URL

Using URL ensures that a copy of the attachments is brought into the connection specified in Connection to reports storage (Optional, advanced).

Lasernet will receive instructions to pick up the attachments from this connection/storage and delete the attachments after they have been processed (such as after emailing/printing the document).

It is possible to have connections for different storage types (hybrid), such as Azure, File and SharePoint.

Warning

Concern: file naming and concurrent (high) sessions/users processing and when re-using same document/attachment.

The link to the attachments in Sharepoint is parsed within the XML file.

Base64 file

Attachments are Base64 encoded into the XML file and multiple attachments are supported.

Lasernet decodes and adds the attachments as part of the process (email/print) and there is no need to remove any entries in a Storage (File, Azure, SharePoint) as everything is Base64 encoded into the XML file.

It is possible to have connections for different storage types (hybrid), such as Azure, File and SharePoint.

No concerns in relation to file naming.

URL XML

The system will ensure a copy of the attachments exists in the connection/storage specified in the Dynamics 365 connection to report XML data files storage.

After processing, Lasernet will remove this copy of the attachments.

It is possible to have connections for different storage types (hybrid), such as Azure, File and SharePoint.

Warning

Concern: file naming and concurrent (high) sessions/users processing and re-using same document/attachment).

URL Original

The original location of the attachments is parsed to Lasernet. The following example shows that the original location for the attachments is SharePoint but the connection between Lasernet FO Connector and Lasernet is using Azure (Service bus queue and Azure Storage).

"URL/Link" to the attachments is parsed within the XML-file.

Remember that it is possible to override/set the encoding in the report. Enabling the Deliver as Base64 has the highest precedence and overrides the setting in the Lasernet server. Having it disabled respects what is specified in the Lasernet server.

Improved document handling

This version introduces the option to specify whether the Document and/or Custom file should be saved or not.

This feature provides the option to skip saving of the Document (normally a PDF file) and/or Custom file (EDI, XML, Excel, Word etc.) in the Document handling.

Multiple designs link to the same record within the Archive

This version is introduces an option to support different reports/designs linked to the same entry/record within the Journal.

This is located in the Form links for the report.

Examples

What’s used (Example)

What’s used provides the option to identify which tables and fields are used within the Lasernet Design.

Additional and unused tables (patterns) and fields (re-arranges) can be added in Lasernet FO Connector and Lasernet.

Normally, tables in Lasernet FO Connector are represented as patterns within the Lasernet Developer, while fields are represented as re-arranges.

In future versions of Lasernet FO Connector, What’s used will be improved and will provide the option to import/include the XML transformer(s) from the Lasernet Server.

What’s used is enabled in Lasernet > Setup > Parameters > Performance.

What’s used is located within the Structure (Elements) and within the Query wizard.

Lasernet > Common > Reports > Structure

Lasernet > Query wizard > Tables

What’s used exports the Form’s design from Lasernet and imports it to Lasernet FO Connector.

Once the design is imported, Lasernet FO Connector will be able to show what is used in relation to the design in Lasernet Developer (which data sources/tables and fields are used for the patterns and re-arranges within the Lasernet Developer).

The following steps describe the process:

1. Export the required form from Lasernet. It is possible to make an export containing multiple reports.

2. Either make the export from the form list by selecting the required form, right-click, and select Export,

OR

click File in the top menu and select Export Objects.

3. Click Forms and select the required forms.

4. Provide a file name, such as SalesInvoiceReplacement in the following example.

5. Locate What’s used in Lasernet FO Connector, either within the Structure or the Query wizard.

6. Select Upload.

7. Import the file containing the Lasernet forms/design, in this case, SalesInvoiceReplacement.

8. Toggle the following buttons to Yes: Activate What’s used highlighting, Highlight used, Highlight not used.

9. Close the form. The used and unused tables (patterns) and fields (re-arranges) are respectively Green and Red when all three settings are turned on.

Example from Structure (Elements):

Example from the Query wizard:

Tables

Fields

It is now possible to remove fields and/or disable data sources/tables.

Always ensure you have a backup of both Lasernet FO Connector and Lasernet before making any adjustments. Also, remember that it is possible to schedule a backup of Lasernet FO Connector (weekly, daily, etc.). For more information about backup scheduling, read our Lasernet FO Connector User Guide.

Use Update design when you are disabling data sources/tables or when disabling Create element for the data sources/tables.

Update design can also assist in ensuring everything is included after a modification.

Removing unused fields should not require any update of the design.

Use Reset to overwrite an already imported Design/Form.

What’s used also provides the option to search for the Input and Output objects used in Lasernet.

This tool searches across all patterns, which is extremely useful in the case of multiple patterns. It also provides an overview with the possibility to group items together.

It is also possible to adjust Input and Output objects, and export these from Lasernet FO Connector to then re-import the Form into the Lasernet Developer.

Another advantage of removing unused tables and fields is the improved performance as removing unused information will lower the size of any generated XMLfile.

This can also speed processes up in case many records in a table are unused.

Update design (Example)

The option to auto-update a Lasernet design is the outcome of our effort to improve the interactions between Lasernet and the Lasernet Connectors, such as Lasernet FO Connector .

It is located at report level: Lasernet > Common > Reports.

Update design is not enabled by default but can be enabled in the following location: Lasernet > Setup > Parameters > Performance.

The following steps describe the process:

1. Ensure the Layout for the Query/Report (here SalesInvoiceReplacement) is set to Minimum. Ensure the last Grab/XML file is run with Layout set to Minimum as well.

2. Export the required form(s) from Lasernet. It is possible to make an export containing many reports. Either make the export from the form list by selecting the required form, right-click, and select Export,

OR

click File in the top menu and select Export Objects.

3. Click Forms and select the required forms.

4. Provide a file name (AllReports in this case).

5. Locate the report in Lasernet FO Connector or select the report when opening Update design.

It is possible to select the report from the lookup Report name.

6. Click Upload.

7. Select the exported file containing the form(s) from Lasernet.

8. Ensure a Grab file is selected.

No modifications should be shown at this point.

9. Change the Layout from Minimum to Maximum within the report’s Query wizard.

10. Re-run the report.

11. Re-open Update design.

Modifications are now shown when selecting the newly created Grab file.

12. Download the modifications, either by using Download updated file or the Download icon. It is possible to create a new version by using Create new design version.

13. Import the newly created .Inobject file into Lasernet.

14. Patch or Commit and Deploy in Lasernet.

15. Re-run the report in Dynamics.

New re-arranges are now adjusted and used with Lasernet (the patterns and re-arranges are changed in Lasernet).

• Layout: Maximum

Contains the sections Detail collection and Detail

Within the Lasernet Developer:

Within Update design in Lasernet FO Connector:

• Layout: Minimum

Within the Lasernet Developer:

Within Update design in Lasernet FO Connector:

Bug Fixes and Enhancements – Lasernet FO Connector 6.19

375775@LAC365FO: Translations are now displayed next to languages in “Select languages”

When adding labels in the Report group in Lasernet FO Connector 6.19, the translations are now displayed next to the languages shown in Selected languages.

Location: Lasernet > Setup > Lists > Report group > Add label(s)

Previous version of Lasernet FO Connector

Lasernet FO Connector 6.19

375720@LAC365FO: Name of dialog fields is “Text ID” instead of “Control name”

Language/label ID was shown when using From default. This is now fixed for a field in the dialog setup.

LAC_Label_Text (not LAC_Label_Id) should be shown when executing the Query report.

375668@LAC365FO - Data Source replacement does not work when copying a subreport from one report to another

A problem used to arise when copying a subreport from one report to another: despite choosing what to replace, the data source/table was not properly replaced.

This has been fixed.

The following example shows that the data source/table CustConfirmJour should be replaced with the data source/table CustInvoiceJour when copying the subreport from the report SalesInvoice into the report SalesConfirm.

375405@LAC365FO - Issue using filter within the structure when using the task recorder (playback)

In previous versions it was not possible to record the use of a filter in the report list and within the Structure/Elements.

This meant that the recorder did not find the intended report when running the playback.

This has been fixed: it is now possible to use a filter for both the report list and within the structure/elements.

Search for a value within the structure/elements:

The task recorder did not include the steps used for the filter:

374919@LAC365FO - Typo in warning message in the Query wizard

A typo was found in a warning message in the Query wizard. The word “reference” was spelled as “refference”: this has been corrected.

375463@LAC365FO - Incorrect Help text on Document handling destinations

All help texts for the destinations in document handling have been changed as they did not match the “Document handling” tab.

374045@LAC365FO - Remove destination type from “Print to” lookup when working with handheld devices

In Lasernet FO Connector 6.19, all printer names have been modified to exclude “Lasernet Print:” for enhanced readability in the Warehousing app.

374026@LAC365FO - Report attachment from Archives/Attachments - Parameter needed for maximum number of attachments in an email

In Lasernet FO Connector 6.19, it is possible to set a maximum number of attachments to an email.

In the previous version, the maximum number of attachments was set to 100 and not adjustable.

Location: Lasernet > Setup > Parameters > Performance

In the case of a non-specified maximum limit, when there are 101 attachments, the system will automatically default to a limit of 100 attachments, thereby excluding the final attachment from being added and sent.

371669@LAC365FO - Updated and added report elements loading for new SSRS report

The following prompt is shown when creating a new report, asking whether the structure/elements should be created:

Previous versions of Lasernet FO Connector required to load the elements/structure from Reload report fields when adding a new SSRS report.

371578@LAC365FO - Expression editor should maintain minimal height so it is always visible

The Expression editor now has a minimum restore height so that it is always visible.

Minimizing the editor will result in it being adjusted to a minimum height to ensure it does not require to be resized in case the height is set to low.

371012@LAC365FO - Incorrect labels from method added to Structure

Having two display methods with the same label added the label only once to the XML file.

371038@LAC365FO - Report group > Add label(s): “Is one of”/”Matches” does not work as expected (Changes made to “Add label(s)”)

When opening the Add label(s) tab in Report group, the Label location is now set by default to “Labels cache” instead of “System” as in the previous version of Lasernet FO Connector.

In the previous version of Lasernet FO Connector, the search filter option “Matches” did not return any record(s).

This has been updated.

It is possible to configure a custom view containing the required languages.

When working with labels/language texts in Lasernet FO Connector, customized views provide the option to exclude all not needed languages. Follow these steps:

1. Filter all needed languages.

2. Click the Stand view dropdown and select Save as.

3. Provide a name and enable Pin as default view as this will ensure the view/filter is used by default next time the form is opened. Only needed languages will be shown.

371607@LAC365FO - Email body missing from “Review before sending” screen and email body changing when swapping between destinations on “Destinations” page

The email subject could show as empty when using predefined destination and review.

The email is properly be delivered only when the email body is configured within the predefined destination.

Lasernet FO Connector 6.19 ensures the proper email subject is shown when using predefined destination and when using review.

370631@LAC365FO - LAC export/import - Added "Filter and select" option to the report selection (Added possibility to filter and select reports by name)

When exporting more than one report, the system required to select all the reports manually.

A filter has been added: all reports found through this filter will be selected.

This is extremely useful in relation to the task recorder as it provides the option to Copy, Export and Import the proper reports by using this new filter.

369465@LAC365FO - WHSPickListProduction report always loads print management only fix

Standard Dynamics 365 Finance and Operations always uses the setting from print management when printing the Picking list report, regardless of what is specified within the printer dialog.

A fix, which users can disable/enable, has been added as part of the hotfixes.

Enable fix

System administration > Setup > Hotfixes from Lasernet

This fix updates the print destination setting that is specified in the print dialog.

With/Without fix enabled

Warehouse management > Outbound waves > Production waves > Closed wave

It is possible to change the Destination of the Pick list when attempting to print the list.

363892@LAC365FO - Changing Lasernet Connector query report batch job parameter > Object reference not set to an instance of an object

In previous versions of Lasernet FO Connector, it was not possible to change the parameters of a batch job on a Query report.

An error like the following was thrown:

Error

Object reference not set to an instance of an object.

This has been fixed.

348230@LAC365FO – Problems creating Tutorial query LACTutorialCustomCode

The following error was thrown when using the Create report located in Lasernet > Setup > Tutorial > Query based reports.

Error

Original value source was not found.

This has been fixed.

345699@LAC365FO - Adding “Deliver as BAs64” in Attachments form, instead of confusing AttachmentDeliveryMode enum field (Change to “Report attachments” field inside attachments)

In the previous version of Lasernet FO Connector, the Report attachments field was a dropdown.

This has been changed to a toggle button.

343705@LAC365FO - Question: Possible To Change LanguageId on CE Report Using IF Statement

An option to limit the available languages when running a report from Microsoft Dynamics 365 Customer Engagement has been introduced.

This avoids all languages for the report from being listed within the printer dialog in Lasernet FO Connector/Lasernet CEConnector.

Lasernet > Dataverse/Dynamics 365 > Entity reports

The option will be presented as follows within the printer dialog in Dynamics 365:

Enable Allow language enforce for the Report/class report, in case this new option is used. This is located in Lasernet > Common > Reports > Security.

The Report/class report is found in Lasernet > Dataverse/Dynamics 365 > Entity reports > Report name.

In Lasernet FO Connector 6.19, it is possible to identify from which company a Report/Class report should be executed.

Previously, the company/legal entity was ‘locked’ to the company associated with the user used for granting permission (consent).

345347@LAC365FO - Expression editor - Context.EventLink

The following warning was thrown within the Expression editor after selecting EventLink from the Context:

Warning

Unknown value in Context.EventLink_000268. object: at position “<-!->Context.EventLink_000268.”

A possible workaround was selecting EventLink through the dropdown instead of the Expression.

344479@LAC365FO - Check ‘Selecting Query from class’ throws object error (Custom code checkpoint)  (Query wizard error occurring when choosing the Query source: “Query from class”)

The following error message occurs when choosing the query source “Query from class” in the Query wizard:

Error

Object reference not set to an instance of an object.

This error no longer occurs.

370476@LAC365FO - ReportValue in Group by (Use group by on report values)

In the previous version of Lasernet FO Connector, it was not possible to use “Group by” for report values within the Elements/Structure.

353833@LAC365FO - Aggressive GC collection

An option to enable an ”Aggressive Garbage collection” has been introduced in Lasernet FO Connector.

It will ensure memory is kept low by doing a Garbage collection after each report execution, as well as add additional execution time.

It should only be used/enabled for debugging purposes or if an environment is slowing down over time.

Use Top picking in T&P to verify/validate the time overhead added by running a number of reports with and without Aggressive enabled.

No impact if this setting is used when running reports through a batch task as the behaviour at a batch server is slightly different compared to non-batch.

Aggressive GC

Aggressive garbage collection after each report execution. Use this if you experience your environment memory rising, or slowing down at the end of the day.

Top picking in T&P for validating overhead:

374062@LAC365FO - Report attachment form Archives/Attachments - Parameter needed for Maximum of attachments limit

In Lasernet FO Connector 6.19, it is possible to set a maximum number of attachments to an email. In the previous version, the maximum number of attachments was set to 100 and not adjustable.

Location: Lasernet > Setup > Parameters > Performance > Maximum number of attachments

In the case of a non-specified maximum limit, when there are 101 attachments, the system will automatically default to a limit of 100 attachments, thereby excluding the final attachment from being sent.

367917@LAC365FO - Currency format for “de-ch” is wrong

The number formatting for the Language/Culture xx-ch has been updated.

336040@LAC365FO - Add Descriptions to Lasernet Roles (All Lasernet roles now have descriptions)

Descriptions (help text) have been added for the Lasernet roles.

335020@LAC365FO - Lasernet Original Preview creates archive record as a “Copy” (Fixed: resend of “Original preview” being assigned to “Copy”)

In the previous version, all records of SSRS reports were created with the property “Copy” set to “Yes”. This happened if the “Dialog options” of SSRS reports were “Run to specified destination”.

This has been fixed.

342044@LAC365FO - Wrong writing direction in Review before sending email fields

Writing direction was sometimes changing from Right to Left (RTL) within the Review of a document.

This happened when either typing within the existing context or when “marking” (blur) and adjusting, or deleting existing information.

It happened for the fields Email, Cc, Bcc.    

Marking and deleting existing information:

Writing direction RTL when typing (like Kim.Agerholm@Formpipe.com in the following):

This has been fixed by forcing the proper writing direction.

It is normally not required to specify a writing direction. However, this feature is added to avoid any situations in which writing directions are changed.

341301@LAC365FO – Support for multiple reports/designs from the same Journal

Static report

Use this option to restrict buttons to a specific report and display the Archive section exclusively for that report.

If the Static report option is not enabled when having multiple buttons and planning to run different reports, the business process will determine the report dynamically and the Archive will display entries associated with the current record.

This option is introduced to help those who have different reports/designs linked to the same record within the Invoice journal.

The previous version of Lasernet FO Connector only used the Reference (Ref record) between the record in the standard Journal and the Lasernet Archive to identify whether a document already existed.

If a related record was found, the system enabled the Archive button and showed the original/copy of the document without having to use Force rerun. The system would just pick up the existing document from the Lasernet Archive.

Example: two versions exist of the same report, such as when a customer changes the output/layout (Query) over time.

• Old-version of the report

Report name: SalesInvoiceReplacement_Old_Version

No entry is present in the Lasernet Archive and the Archive button is disabled. Using Lasernet Original preview/Lasernet Copy preview would need to use Force rerun as no documents/entries are found within the Lasernet Archive.

Archive is enabled after either using Lasernet Original Preview or Resend (similarly for the Lasernet Copy Preview).

• New version of the query

Report name: SalesInvoiceReplacement_New_Version

Using Resend from the Archive enables the Archive button even though the report has not been processed through the new report - SalesInvoiceReplacement_New_Version.

This is fine when a customer would like a 100% trustworthy archive. In other scenarios, customers want to ensure the new (not the old) version of the report is rendered.

This option is provided through the Static report:

Lasernet > Common > Reports > Form links

The Archive button for the new version of the Report/Query is now disabled as the system is aware about it. The reference between the standard Journal and Lasernet Archive should also take the report name into consideration.

A similar situation arises when a customer starts by using SSRS reports and, over time, moves to replacement reports.

Another scenario sees multiple buttons brought into the same Form. Each button has its own report. Without Static report enabled for the reports, the system uses the first processed report for the other reports as well:

341300@LAC365FO - Lost focus in New expression editor when deleting existing information

In previous versions, focus was lost within an expression when removing an already selected value from a segment, such as when “blurring” and deleting an already existing field. This would require refreshing the session (F5).

The same issue arose when deleting already selected values within the Expression editor.

The selection would appear in the upper left window/corner and not as part of the lookup within the expression.

This version keeps the proper focus.

Focus might still be lost in case of selecting a non-existing field but it is still possible to re-select the value in the selection list in the upper left corner.

338297@LAC365FO - T&P - Checkpoint export/import

The controller pack containing information about how a report should be executed when using Force re-run from the Lasernet Archive was not included when exporting a checkpoint used within the Test & Performance Suite (T&P).

The controller pack has been added as part of the export in Lasernet FO Connector 6.19.

337986@LAC365FO - Corrupt Export from Update design

Update design can adjust an existing design in Lasernet when the output/structure is changing, such as when increasing or decreasing the Layout.

A higher layout adds additional sections like the Detail collection and Details as part of the output (XML file).

Adding the sections Detail collection and Details is in many situations quite useful as it provides the option to gather and collapse information.

It is specially useful when preparing a design as it often provides a much easier and readable structure.

However, in other situations, Detail collection and Details are not required and this is the reason why the option to set the Layout (structure) to Minimum was introduced.

Updating the design could lead to a situation in which the Form was not recognized when re-importing the Form back to Lasernet.

This issue has been fixed in Lasernet FO Connector 6.19, where Form is properly recognized.

337832@LAC365FO - CE query attachments, attachment reference table extra”.” when refreshed

A “.” was added as postfix for the attachments when using a Class report (CE/DataVerse) and after finishing the Query Wizard. Lasernet FO Connector 6.19 does not add this “.” after finishing the Query wizard, and attachments work as expected when using a class report.

375996@LAC365FO - Validation for non-existing SharePoint setup in std.

In previous versions, the following error was thrown when validating the connection, when no Default SharePoint server was configured in Lasernet FO Connector.

Error

Object reference not set to an instance of an object.

Setup of the Default SharePoint Server in Lasernet FO Connector:

The following error message is thrown in Lasernet FO Connector 6.19 when trying to validate a connection for which no Default SharePoint server has been set up.

Error

No default SharePoint server defined.

377016@LAC365FO - Expression Editor Nested if Statement not working

Using nested IF statements such as the following was not properly evaluated.

Expression:

If ( SalesLine.ItemId = "P0001" ) Then ( "This line item is P0001" ) Else

( If (  SalesLine.ItemId = "D0004" ) Then ( "This line item is D0004" )

Else ( "This line item is neither P0001 or D0004" ) )

This has been fixed.

375735@LAC365FO - Button to add multiple languages to one or more language texts (Faster to add multiple languages to language texts)

In previous versions, it was only possible to add one language and one text at a time.

A new option allows adding multiple languages to multiple texts which makes it much faster and easier to add translation(s).

337171@LAC365FO - Blank screen if ‘Previous in new browser tab’ is enabled

An issue arose when previewing a document for which the file format was set to a separate browser tab.

The document was properly shown within a separate browser tab.

However, the main window from where the process was started would show a blank screen:

336810@LAC365FO - Add copy button back into Azure storage connection

The option to copy the Connection used for the Queue and for the Storage is added in the Form for the Lasernet servers and into the connections for Lasernet.

Having the option to copy a connection in the Lasernet servers makes it much easier to maintain/prepare the configuration for Lasernet. This is because it is possible to copy the connection for the Queue and for the Storage directly from the setup of the Lasernet servers.

To configure the interaction between Lasernet FO Connector and Lasernet, follow these steps:

1. Copy the connection for the Queue (normally a connection for an Azure ServiceBus Queue) from Lasernet FO Connector.

2. Paste the connection into the Azure Service Bus module in Lasernet.

3. Copy the connection for the Storage (normally a connection for an Azure Storage) from Lasernet FO Connector.

4. Paste the connection into the Command for the Azure Storage.

Minimum configuration

It is possible to configure an environment in which the Outgoing connection is the only connection needing to be configured in the Lasernet servers.

Lasernet FO Connector will parse the connection named Azure Storage in case this field is left empty within the Lasernet servers.

These steps describe the process:

1. Copy the connection from Lasernet parameters in case the connection is left empty for the Azure Storage (Lasernet > Setup > Parameters > Performance).

2. Paste this into the command named Azure Storage within the Lasernet Server.

3. Locate the connection within the Lasernet Server and find the one named Azure Storage.

4. Paste the Connections from Lasernet FO Connector.

5. Either Patch or Commit and Deploy in Lasernet.

6. Use Validate to ensure everything is configured and working as expected.

366107@LAC365FO  - Reload label error (Change and fix to “Add label(s)”)

Location: Lasernet > Setup > Lists > Report Group > Add label(s)

“Reload labels for current viewing language”

In previous versions of Lasernet FO Connector, an error was thrown when loading labels for the current viewing language.

This error has been replaced by the following warning:

336587@LAC365FO - Review before sending form is not opened if Preview in new browser is enabled

Enabling the preview in a separate browser tab caused the review of the document to be shown in a separate browser tab/window and not in the current review tab.

Lasernet FO Connector 6.19 always keeps the document inside the existing review tab, even when preview is set to separate browser tab/window.

Setup of preview for a file format is located in Lasernet > Setup > Lists > File formats.

336423@LAC365FO - Form research when inserting new dialog fields within the dialog setup (New parameters in “Dialog setup move to the top (Fixed))

In previous versions of Lasernet FO Connector, newly created dialog fields (parameters) in Dialog setup were moved to the top.

This has been improved: the newly created dialog field stays in the proper position.

335020@LAC365FO - Lasernet Original Preview creates archive record as ‘Copy’

Using the Lasernet Original preview without having any documents in the Lasernet Archive used to mark the Lasernet Archive entry as a copy.

This has been fixed.

3357007@LAC365FO - Report attachments: First/Last are not always returned if there is more than one attachment with the same timestamp

Using From Archive in an attachment, with either Last or First to find the attachments, has been improved in Lasernet FO Connector 6.19.

In previous versions of Lasernet FO Connector, it was not possible to distinguish documents within the Archive if they had the same timestamp.

Lasernet FO Connector 6.19 uses RecId as well as CreatedDateTime to find either the Last or First attachment (document from Archive).

This approach ensures the proper document is found within the Archive even when the documents have the same timestamp.

In previous versions of Lasernet FO Connector, using either Last or First in combination with the From Archive caused an issue if the documents found within the Archive had the same timestamp.

331259@LAC365FO – New Expression editor error: 'Unknown value in # object'

Using information/fields from the Parameter for a replacement report used to throw the following warning in an expression.

Warning

Unknown value in Parameter. object: at position "<-!->Parameter."

This is fixed.

336369@LAC365FO – Option to use Custom properties in T&P/Top picking (Background print)

Customer properties are supported for Background print of a report/report-design.

This is useful when multiple designs are required for a report or in case of a special internal (or debug)version of a report is required.

An internal/debug version of a report could have additional information that is only required for internal use or useful to identify issues in a report.

331129@LAC365FO – T&P – LAC Archive - Destination description missing

The description from the predefined destination (Destinations) was not shown in the Lasernet Archive.

This is now fixed, when a destination is found (and included in the XML file).

331106@LAC365FO – T&P - Top picking 'Unprocessed only' can update same document twice

Using “Unprocessed only” through the Top picking within a batch task caused same documents to be “re-processed” multiple times when running the batch with a high frequency (or long running documents).

Lasernet FO Connector 6.19 does not re-process the same document multiple times when using the batch-scheduler for repeating the same batch-job.

Unprocessed only and batch-scheduler in previous versions:

Lasernet FO Connector 6.19:

Ensure Recurrence is used to schedule the batch job.

330896@LAC365FO - Warning while importing report (minor issue)

The following warning could appear when importing report(s), but would not cause any issues when running the Report.

This warning has been removed.

Warning

Could not find a matching LACArchiveForms record for LACReportParameter. Have LACArchiveForms been selected for import?

330175@LAC365FO – Feature request: Role for T&P batch print scheduling

The following permissions are granted/added to the Lasernet advanced user role.

Manage checkpoints:

Parameters for Background print:

329833@LAC365FO – Option to select an "alternative" destination when reviewing a document

An option to select an alternative destination when reviewing a document has been added.

In previous versions of Lasernet FO Connector, it was only possible to deliver to the same destination as the one selected before reviewing the document.

In Lasernet FO Connector 6.19 it is possible to select/alter any destination (apart from the predefined one) by using Change when reviewing the document.

Review is useful in case the document needs ”clear verification” before printing or sending as an Email.

This option is also useful in case additional attachments like a “Bill of lading” should be attached before delivery.

329543@LAC365FO – T&P: Checkpoint form set in descending order by date/time so that newest is on top

The sort order in the form containing the Checkpoints is adjusted and is now showing the newest entries (records) on top.

329358@LAC365FO – Print Buttons - Not Showing up on Quotation Journal (Similar: ProjInvoiceJournal)

Adding print destinations/print buttons defined in Print buttons > Common > Direct printout destinations was not shown in form like Quotation Journal and ProjInvoice Proposal.

The form design/patterns for these forms was not the same as the other Journal forms in standard Dynamics D365FO, and it was the reason why it was not possible to add the buttons on the fly (runtime).

Form: Quotation Journal

(Sales and marketing > Sales quotations > All quotations > Quotation journal)

Form: ProjInvoice Proposal

(Project management and accounting > Project invoices > Project invoice proposals)

329143@LAC365FO - ProjTable and ProjSorting Table Relationship in Query Wizard

Using an ”Array field” as part of a relation did not properly save the relation after closing the Query Wizard.

Example: sortingId[2]

ProjTable - Definition of ProjTable in SQL

348562@LAC365FO - Adding ‘Related Tables’ under sub-queries in the Query Wizard

In the previous version, it was not possible to add a related table to a parent subquery.

This has been fixed.

Location: Lasernet > Common > Reports > Query wizard

Choosing a “CustTable” as the parent table:

Adding a subquery to the parent table (CustTable):

Trying to add a related table to the parent subquery:

Copying the Connection to clipboard:

328706@LAC365FO - OData based subreport behaves incorrectly when added to a Query based report

In previous versions, having a subreport using OData fetch data from, for instance, Dynamics 365 Customer Engagement (DataVerse) did not properly add the ranges for the subreport.

This is fixed.

325678@LAC365FO - CSS timer for long processes

The option to enable a timer for the “progress bar” has been added.

This is useful when benchmarking and adding a report, as standard Dynamics does not always measure/show the proper progress and the progress is often only updated every five seconds.

The new timer is activated at: Lasernet > Setup > Parameters > Performance

The timer will measure and show the progress by the second.

325259@LAC365FO - T&P: Alert on Background print function end

The option to use Alerts is introduced for the Background print: it provides the option to get a notification once documents have been delivered to the Lasernet server.

The option to use Background print is located at Lasernet > Common > Reports > Form links.

In order to have the Backround print in a Journal, it is necessary to configure it for the Journal and for the Report as it is possible to have different reports in the same Journal.

Once configured, Background print will be shown as follows in the standard Journal for the Report.

Use Alerts to configure how to receive the notification once the document has been processed (delivered) to Lasernet.

A notification is provided through either the ”pop-ups” or an Email.

324366@LAC365FO - Missing data in XML if Sort by is added to Group by query

Adding a sorting on top of a Group by query used to cause a missing output in case the query contained more tables/data sources, or no field was added from the parent data source.

This is similar to having a Group by query consisting of the data sources/tables SalesTable and SalesLine for which no fields are added for the data source/table SalesTable.

A sorting is added above the field LineAmount.

324208@LAC365FO – T&P - Generate report summary - Error: Root element is missing

A warning was thrown when generating the Report summary, when the last entry in the Lasernet archive had an ”invalid” reference to the XMLfile, such as restoring an environment.

Lasernet FO Connector 6.19 does not throw this error (a work-around in previous versions was to run and prepare a proper XML file for the Lasernet Archive).

323710@LAC365FO - Direct jump from preview form or archive form to Report configuration

A new option is introduced to jump from the preview of a document to the report.

Example:

Clicking Report in the preview will open the report configuration for the Report shown in the preview.

It is also possible to open the report configuration directly from the Lasernet Archive.

316147@LAC365FO - Email defaults of Company/Report are not executed when resending a PDF (without Force re-run)

Resending an existing document (without Force re-run) from the Lasernet Archive did not apply the From name and From e-mail defined within the Lasernet parameters, when the previous document was not processed to an e-mail.

This has been fixed.

308788@LAC365FO - Parameters with spaces in their names no longer result in errors in the Expression editor

An error was thrown when accessing parameters containing a space within the Expression editor.

This error no longer occurs.

299787@LAC365FO - Not possible to use added functions with identical names from different tablets/classes

Lasernet FO Connector supports the option to add a function even when the same function/method exists in several tables in Dynamics 365.

It is possible to add functions/methods from either the expression or the Lasernet parameters.

Adding a function from the Expression editor:

Functions in Lasernet FO Connector provide the option to ”re-use” existing functions/methods from the application.

Remember to clear the Lasernet Cache in case new functions/methods are added.

Provide a unique name within the Name in expressions as this is the name shown within the Expression editor.

It is also possible to ”name” and create new functions in the Expression function located at Lasernet > Setup > Parameters > General > Default values.

271957@LAC365FO - #21778- D365FO LAC: Decouple XML and PDF storage for SharePoint 365

Two new useful options are introduced in relation to Report attachments:

• URL XML

• URL Original

They are especially useful for attachments in SharePoint as they allow to parse the attachment(s) through a reference to a temporary location within the Azure Storage.

The following two new options are located at Lasernet > Setup > Administration > Lasernet servers:

URL XML

In the following example SharePoint is only used in Lasernet to save the documents (PDF files). The Azure Service Bus Queue and Azure Storage are used for communication between Lasernet FO Connector and Lasernet.

In Lasernet FO Connector, attachments are saved in SharePoint.

Using URL XML will save a copy of the attachments into the Storage specified in the field D365FO connection to report XML data storage (Optional, advanced).

Using this option is advantageous because it avoids using SharePoint for communication between Lasernet FO Connector and Lasernet as this could cause throttling issues in SharePoint.

Attachments parsed through the Azure Storage are removed in Lasernet once used.

No adjustments are required within the Lasernet configuration as it reuses the same generic logic that is already used for attachment(s).

URL Original

Using URL Original will parse a URL to the original location of the document and Lasernet will use this URL to add the attachment.

In the following example, the attachments are saved in SharePoint, which in turn is configured for the following Default Sharepoint server, Site, and Folder.

The Default SharePoint server is located at Organization administration > Document management > Document management parameters > SharePoint.

The document type (Site, sub-site/folder) is located at Organization administration > Document management > Document types.

The following, in relation to the connection documents_auto_sharepoint, only applies to the legacy in Lasernet and is not required when Graph is used.

A connection such as the one displayed in the following image is required for parsing/providing the proper URL to Lasernet as attachments in standard Lasernet FO Connector are not saved in the same location as the attachments used with/in Lasernet FO Connector/Lasernet.

Create a SharePoint connection documents_auto_sharepoint:

Benchmark/comparison between URL XML & URL Original

The Test & Performance Suite (T&P) is used for benchmarking performance.

Benchmark is at a Tier-1 Dev-box; Service Fabric (SF) environment is not used.

Processing 10 documents which are having the same attachment:

An attachment (PDFfile) containing the General Terms and Conditions of Sales and Delivery is added to all confirmations.

232282@LAC365FO - Better validation of Email/syntax

205376@LAC365FO - Validate email syntax

Lasernet FO Connctor 6.19 validates email addresses entered within the "printer dialog". We received feedback from a PEAP customer who got warnings as their master data contained many spaces and a ; (semicolon).

It is possible to configure the validation of email addresses through a RegEx (Regular Expression) but also to completely avoid this validation, if needed.

It is best practice to have a validation of the entered email addresses as this can often prevent errors at the start of a process.

The regular expression for validating an email address is located in Lasernet > Setup > Parameters.

Use the value .* within VALIDATION to have the system accept any values. Only use this as a workaround as it is preferable to have a stronger and more strict validation as this could avoid potential issues.

Avoid validation of the email address

Using .* will make any value acceptable.

Example of accepted space before ; (semicolon) but not afterwards (standard in 6.19)

Entered email addresses: kim.agerholm@dynazure.cloud; Kim.Agerholm@Formpipe.com

VALIDATION

^([a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}(,\s{0,}|;\s{0,}))*[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$

Example of unaccepted ; (semicolon) and space (current standard in 6.19-PEAP)

Entered email addresses: kim.agerholm@dynazure.cloud;Kim.Agerholm@Formpipe.com

VALIDATION

^([a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,},)*[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$

354024@LAC365FO - T&P: Checkpoint creation from Top picking report processing (PDF comparison – Add checkpoints through Top picking in T&P)

It is now possible to automatically to create ‘Test points’ through the Top picking located within the Test & Performance suite.

Location: Lasernet > Test and performance suite > Performance > Batch print schedule (Top picking)

This feature creates both checkpoints and a Test flow containing all the checkpoints. It also makes it much easier and faster to create the required checkpoints.

382090@LAC365FO - Lasernet button now includes logo

Location: Lasernet > Setup > Parameters

It is now possible to specify which text and image should be shown on the buttons used in the Lasernet FO Connector.

This includes a preview that shows what it will look like for an end user.

Select None if no image must be shown.  

‘Lasernet’ is the default text option, when no label or language text are selected.

Similar options exist within the Form links: specifying Menu label, Label, Menu Image and Image will overwrite the settings specified within the parameters for the Lasernet FO Connector.

382541 - T&P: UX Test > Form personalisation – visualisation

Location: Lasernet > Test and performance suite > Test > UX tests

It is now possible to see the ‘form views’ used at the time of the recording.

It is also possible to reset all the views saved as part of the recording, by using Reset form views.

Using UX Test for the playback of the task recording will include the saved Form views from the time of the recording, and use them as part of the playback.

Changes to Default Configuration/Demo Setup

341412@LAC365FO - Lasernet: Missing # in the module for OutSharepoint

A postfix # was missing in the module OutSharepoint within the Pre JobInfos.

338567 - Support 338567: LAC Default Config Update for Cheque_USReplacement for 6.19

The following is added in the default/demo-configuration for the SSRS Report Cheque_US and the replacement report Cheque_USReplacement.

Added to ensure unique filenames; having non-unique filenames can cause duplications and missing reports.

Test & Performance Suite

Some extremely useful features have been added to the Test & Performance Suite (T&P).

• Task recorder

• Ignore usage data (task recorder)

• New layout for printer dialog - “Tabbed form” (table of contents)

• Support for XPath validation (XML file)

• Ignore/reset personalization of Form(s)

• Support for Filter in report overview and within structure/elements

• Option to re-record from the UX Test

• Filter when exporting and importing reports (to support playback)

Check points

• Automatically compare PDF files

• Option to ignore Jobinfos when comparing XML files

Task recorder

The following two new parameters have been introduced for the UX (User Experience) testing in Test & performance suite (T&P).

Lasernet > Test and performance suite > Parameters > General

Ignore usage data during test recording and playback

Lasernet FO Connector saves much information as usage data (last values).

This could cause issue(s) in the playback of a recording and, therefore, issue(s) if the recordings are used for testing/automatic testing.

Example:

Print confirmation shown in the following image is saved within the usage data (last values) and could cause an issue if the recording does not contain the step for setting Print confirmation.

Playback of a recording for which the Print confirmation is not enabled, or for which the user running the playback does not have the Print confirmation enabled could get a block/stop in the recording.

Test & Performance Suite 6.19 contains the option Ignore usage data during test recording and playback.

Location: Lasernet > Test and performance suite > Parameters > General > UX Testing.

Enabling Ignore usage data during test recording and playback results in ignoring the usage data and, therefore, requires Print confirmation to be enabled as part of the recording. Otherwise, it is not possible to configure the destination.

Print confirmation gets disabled when preparing the recording even if it was previously enabled, as the usage data (last values) are ignored under the recording.

This ensures the recording is prepared from scratch (comparable to having no usage data (last values)).

Disable tabbed print settings form design

Enabling the option Disable tabbed print settings form design ensures the possibility to playback a recording containing a setting for the destination/printer dialog.

In Lasernet FO Connector, playing back a recording containing a setting for the fax, such as the one shown in the following image, can end up setting the wrong destination, causing to either stop the playback or throw an error.

Lasernet FO Connector 6.19 uses “tabbed form” (table of contents) by default for the settings of the destination/printer settings.

This is to ensure the playback of a recording in case it contains a setting for the destination/printer settings.

Having the Disable tabbed print settings form design disabled shows the setting for the destination/printer settings as follows, and ensures the right selection if the recording is used for playback/test:

Filter

The use of a filter in either the report list or within the structure/elements in Lasernet FO Connector was not properly recorded in previous versions of Lasernet FO Connector.

Being unable to have recordings that included the use of a filter could cause the playback of the recordings to stop.

This latest version ensures a complete recording, including the filter, is carried out, both in the report list and within the structure/elements. This recording can, therefore, be used for playback/test.

Validation of XPath

Another useful feature added as part of T&P is the option to validate a value within an XPath.

The option Set task recorder validation path appears when making a recording and when right-clicking the required XPath within the XML file.

Skip Validation of JobInfos

A new option to skip the validation of the information in the JobInfos section within the XML file has been introduced.

This is useful when data has been restored from PROD and information like connection is not the same. The following example illustrates how to avoid different destinations to cause failure:

Re-recording

A new option for re-recording has been introduced.

Re-recording existing task recordings simplifies the process of adjusting an existing recording.

Reset personalizations

Resets embedded form personalizations for the forms used in the recording

Filter for Copy, Export, and Import configuration

A filter is introduced when Copying, Exporting, or Importing reports.

This is added to assist the playback of a recording as wrong reports could get selected.

PDF comparison

It is possible to compare PDF files from the checkpoint in the Archive with the newly created PDF file.

This can be used as part of an upgrade in which checkpoints have been created prior to the upgrade and the PDF comparison is used to validate the documents (PDF files) before the upgrade with the documents after the upgrade.

There is a limitation when using checkpoints with some reports and Force re-run in Lasernet FO Connector.

Reports such as Sales invoices, Sales confirmations, Purchase orders have a journal/journal line, which ensures the possibility to use Force rerun when resending a document.

A report such as Cust account statement does not have any location besides the usage data (last values) and the report. Therefore, it needs the usage data (last values) for storing the required information.

Using this report for a checkpoint would always use the latest execution (usage data/last values) to find the required information needed to run the report from scratch.

Example

The following parameter was applied when preparing the checkpoint within the Lasernet Archive for the report Cust account statement:

When running the Test for this checkpoint, the system lets the user know the test is passed:

The test will show as failing if either the parameters are changed or another user is running the same checkpoint and they have other parameters set for the report (usage data/last values).

Note

The usage data (last values) are saved per user. This can also cause different results when making a comparison.

Throw error

Throw error provides the option to simulate an exception/error. This is quite useful in relation to negative testing.

Location: Lasernet > Test and performance suite > Test > Tools > Throw error

368759@LAC365FO - SameLevel was producing just 1 and 1 record instead of fetching all. Layout generation had to be reviewed

For each table within the Query wizard, it is possible to specify how data should be collected/fetched and added to the output (XML file).

Data is either “Nested” or added at same level as the parent data source (table).

In previous versions, using SameLevel only added one record from the parent data source/table and one record from the child data source/table.

In the following example the parent data source SalesTable was only added once.

In Lasernet FO Connector 6.19, parent data source is added once and child data sources are added as many times as records exist for the child data source.

Remember to enable Fetch/ Fetchmode if records for the child data source need to get sorted at same level as the parent data source.

In some situations, this requires the use of the Fetch/Fetch mode 1:1 for the Query within the Query Wizard.

It is not always enough having the records at Same Level as parent as the Layout is only the representation (XML file) and not the way the records should be fetched through the Query.