Release notes for the Lasernet Connector FO

Stay updated on the latest new features, fixes and enhancements in LAC365

Every quarter there is a new version of the Lasernet Connector for Dynamics 365 FO.

Here, you'll find a list over the new features, fixes and enhancements of a release.

Contact our Account Manager, Kristian Truesen, for more information and/or upgrade path at Denne e-postadressa er beskytta mot program som samlar e-postadresser. Du må aktivere javaskript for å kunne sjå den. or +45 3147 2159.

Release for the Lasernet D365 Connector
for Finance and Operations version 6.18.3

Release date: 14-04-2022

The LAC365FO version 6.18.3 is a quality update for LAC365FO 6.18.2 with a main focus on quality, reliability and stability,

The new version contains the following enhancements:

• Using a replacement (Query) for the French cheque in Dynamics 365
• Printing to predefined destinations on all SSRS reports on LAC 6.18.2 and PU 10.0.31
• Compatible with SharePoint
• Preview in new browser tab

347572@LAC365FO

"Buffer for call of SrsTmpTblMarshaller::deleteTmpTblData is not specified" when printing Cheque Replacement Report

Using a replacement (Query) for the French cheque (Report: Cheque_FR) threw the following Error message:

Buffer for call of SrsTmpTblMarshaller::deleteTmpTblData is not specified. at Dynamics.AX.Application.LACUtils.`Global_StackInfo(XppPrePostArgs _args) in xppSource://Source/Lasernet\AxClass_LACUtils.xpp:line 1299 at

It's recommend that you consider the following when working with cheques in Dynamics 365:

• Resend with force-rerun from the Lasernet Archive is not supported for the cheque reports. This is due to the Microsoft logic of not being able to regenerate the same cheque again – for obvious reasons.

• Having a large amount in the Debit/Credit (13 or more characters) field would, when using replacement, show the following warnings: "The field value is too long Amount and The field value is too long Amount in text"

  The same behaviour applies when using standard SSRS/Report but the warning is not shown – because it would be shown at the Reporting server and therefore is not expected to show in Dynamics D365FO.

347571@LAC365FO

"Object Reference not set to an instance of an object." When printing to predefined destinations on all SSRS reports on LAC 6.18.2 and PU 10.0.31

Using SSRS as the origin for Lasernet reports (a legacy way of working with Lasernet) threw the following error when using predefined destinations: "Error Object reference not set to an instance of an object"

The SSRS report with Lasernet was still generated and delivered. Even though the error message was thrown.

There are no issues when using replacement reports.

346681@LAC365FO

Using SharePoint on PU56 (10.0.32) or newer failed.

Using LAC365FO version 6.18.2 or earlier with Dynamics 365 for Finance & Operation version 10.0.32 (PU56) or later threw the error when using SharePoint for Lasernet.

Lasernet > Setup > Administration > Connections

The error was thrown when entering information in relation to SharePoint (like Subsite, Folder), validating connection/server or when processing a Report to SharePoint through Lasernet.

LAC365FO version 6.18.3 is compliant with SharePoint in both earlier and later versions of Dynamics 365 for Finance & Operations.

347570@LAC365FO

A blank screen was shown if 'Preview in new browser tab' was enabled.

In some cases, Resend (preview) of a document showed an empty screen in the Form from which the Preview was initiated (started).

This was only an issue when having the Preview in new browser tab option enabled Lasernet > Setup > Lists > File formats

An empty screen with no entries (records) would be shown in the Form – see the following example.

Re-showing/re-sending the document from Lasernet > Common > Archive

In some situations, an empty screen was shown.

Result in Lasernet Archive

Expected result in Lasernet Archive

A similar issue occurred when posting and previewing a document such as Sales-invoice, Sales-confirmation and when Preview in new separate browser tab was enabled.

The ‘Preview in new browser tab’ option was also used when reviewing a document in previous versions of LAC365FO.

LAC356FO version 6.18.3 does not use the setting for the Preview in new browser tab but does always show the document within the same browser session/tab.

Enabling ‘Preview in new browser tab’ for a specific file type/format is located in Lasernet > Setup > Lists > File formats

Release for the Lasernet D365 Connector
for Finance and Operations version 6.18.0

Release date: 22-09-2022

The LAC365FO version 6.18.0 is supported with Lasernet version 9 and Lasernet version 10 and a setup for either Lasernet version 9 or Lasernet 10 is required for any new installation and when upgrading from Lasernet 8.

The new version contains major enhancements, many new features including features that can assist in improving performance.

The connector itself has been optimized in relation to performance but this version also contains features that can reduce the content of the XML file and therefore optimize performance.

The main focus in LAC365FO version 6.18 is:

• Performance
• Reliability 
• Usability (user-experience) and flexibility
• Simplicity

See all the major enhancements detailed below.

Autoform DM integration

Archiving for Dynamics 365 made easy

LAC365FO version 6.18 includes an integration of Autoform DM. There are a lot of new features, but the main features are:

• Seamlessly connect to Microsoft Dynamics
• View all documentation for a specific account within the F&O interface
• Search for and retrieve documents quickly
• Share F&O documents with non-D365 users
• Enable access to document sets for customers or suppliers, external of your domain
• Secure storage of all files (PDFs, invoices, video files, audio files) alongside metadata
• Automatic indexing and content type allocation
• Centralized administration and access controls
• A fast and simple Document Import tool
• ISO 27001 compliant

Expression Editor enhancement

Improved guidance when typing

LAC365FO version 6.18 includes an enhanced Expression Editor, which includes new and improved guidance when typing.

This makes typing faster and allows more syntax options. The full range of improvements include:

• A new approach to typing that allows fast type, while catching up with syntax analysis in the background
• Automatic parallel syntax analysis and colors on expression segments
• A new approach for string values – now when using expressions these values can be within single or double quotes
• Multi-line expressions
• Switch–case
• An autocomplete list when typing
• Automatic validation while typing
• Significantly improved error position reporting with a callout indicating the exact place of error
• Enums are introduced as value sources
• The syntax editor area is now resizable
• Comments are introduced
• The overall syntax analyzer and parser performance is improved and various errors are fixed 
• Expression testing is now integrated with the expression editor
• Expressions are fully backwards compatible

Expression typing and auto-complete

The auto-complete function will show up as soon as you start typing in the new Expression Editor. It will automatically filter values based on context of the expression and what has been already typed.

Images on auto-complete lookup will indicate types of available objects.

If you start typing C, the editor will automatically show all available sources starting with “C”. CustConfirmJour and CustConfirmTrans are the tables that are available for the report, and in this example, the SalesConfirmReplacement is used.

If you select or type the table name and continue typing the field name, all available fields and methods will appear in an auto-complete list.

Error reporting

Syntax analysis and error reporting are automatic. If there is an error in the expression, an automatic callout with a short error message will appear, and a longer version will appear in the status line below the editor. Please note that the error position in the status line indicated with <-!->.

Syntax updates

Multi-line expressions are now supported. Comments are also added to improve the documentation of some of the expression parts. For example:

Syntax colors

Syntax elements are now colour coded:

• Blue is reserved to operators and reserved words
• Dark green is for complete value segments
• Dark red is for string constants or numeric constants
• Light green is for comments
• Bright red is for incomplete values. Complete expressions should not contain these
• Regardless of color, underlined segment is “Active”. Value for such segment will be also editable in separate value field.

Please be aware that syntax highlighting can be slow in environments where network latency is high. Because of automatic validation and highlighting, quite a few roundtrips to the server and back are required. You can monitor latency in your browser by navigating to F12 > Network.

An established VPN connection also can slow the performance as the latency can get higher compared to running the software without a VPN.

Enums

There is a new value source called Enums. Enums will also appear in the auto-complete lookup, but only when the filter will reduce the number of them below 20. This is done to avoid loading a massive amount of data, as there are many Enums in the system.

Enums now support three types of values. For example, if SalesTable.Sales status is “Open order”:

1. (New) SalesTable.SalesStatus would return the numeric value of the Enum such as 1.

2. SalesTable.SalesStatus:NAME would return a symbolic representation of the Enum, such as “Backorder”.

3. SalesTable.SalesStatus:LABEL would return label of the Enum, such as “Open order”.

If these are used in expressions, ensure that you compare the same type of value. Best practice is to use :NAME as this will be the same across all environments, even where numeric values might differ.

Auto-complete also works with Enum values:

Test of expression

New functionalities for testing expressions are implemented. You can test expressions with different values that can be plugged into the expression and observe the output result. To test your expression, specify the test values, then click Calculate test result.

All test values are saved as LastValues in the user’s Usage data, under Class > LACExpressionParser > TestValues. The Calculate test result checkmark is also saved in Usage data as Form > LACExpressionEditor > CalculateTestResult. Normally test values can be reused across various expressions, as these are common for all of them. Only relevant values are shown by default, but you can show all test values saved for the user by clicking Show all. Select Clean test values to indicate how many test values are saved for a user.

If the calculation fails, you will get the following test error:

In this case, the expression is technically valid but comparing an integer Enum value with a string produces a testing runtime error.

Misc

The Expression Editor is now resizable.

Support for Sharepoint 365 Graph in Lasernet

Support Microsoft/Lasernet Graphs

A new option to support Microsoft/Lasernet Graphs when working with Sharepoint is now introduced.

The support for Sharepoint 365 Graph in Lasernet can be accessed by navigating to Setup > Administration > Connection > Graph setup in Lasernet.

A similar setting is located in the Lasernet Server which can be accessed by selecting Connections and is also embedded within the Sharepoint module.

Connection for Sharepoint 365

Embedded connection within the Sharepoint module

Enhancements - LAC365FO version 6.18

316466@LAC365FO – Improve warning when resending documents to predefined destination and not use force-rerun

A warning is added for attempts to resend documents by using predefined destination and not using force-rerun.

Force-rerun is required when resending documents and when using predefined destinations, as this would require all data (tables/fields) to identify the proper destination.

312295@LAC365FO – T&P: Top picking for SSRS SalesInvoice and SalesConfirmation

LAC365FO version 6.18 supports the use of SSRS reports for Top picking used within the Test & Performance Suite.

This is useful when there is a need to benchmark report performance and memory when using a standard/customized SSRS report.

305374@LAC365FO - Date format applied on report value is not respected in the Email body

The new option ReportValueFormatted is introduced and issued for using the formatting applied to an element within the structure.

This is useful if there is a need to use specific formatting of information, such as an email body.

Apply the required formatting for the required field, such as the Custom format for ConfirmDate.

305298@LAC365FO - Change in TOP records 6.17

The option Top reset is introduced and used in relation to the Top records.

The Top reset option controls when the number of records used for Top records should get reset/set to zero.

It is possible to use the Top reset for any tables and in any subqueries used within the Query.

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

There is a new option to use one Storage/Storage type for the XML file and another Storage/Storage type for the PDF file.

This approach ensures much better, faster, and more stable communication such as when there is a need to use Sharepoint (or Autoform DM) to archive the documents (normally PDF files).

This is useful if there’s a need for specific formatting of information, such as within an email body.

305298@LAC365FO – Change in TOP records 6.17

The document preview has been adjusted.

317135@LAC365FO – Archive performance sorting parameter

A new feature has been introduced which provides the option to improve performance when there are many entries (records) in the Lasernet Archive and when making a resend from the Archive.

The issue when there are many records is not the resending and creation of the entry in the Archive, but when the selected entry (record) needs to be re-selected (current record).

The default option Newest to oldest, which has also been the standard in previous versions of LAC365FO, could cause the system to become unresponsive when resending from the Archive and when having many entries in the Archive. Selecting the new option Oldest to newest makes the system much more responsive when there are many entries in the Archive and when making a resend. It will find same records but it will set the focus (current record) to the end of the Archive.

Newest to oldest

Records are by default sorted by descending order of the Created date and time, the same pattern of sorting as in previous versions of LAC365FO.

Oldest to newest

Sorting from Oldest to newest will show the newest records at the end of the Archive, in ascending order of the Created date and time.

Release for the Lasernet D365 Connector
for Finance and Operations version 6.17.0

Release date: 01-04-2022

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

The new version contains major enhancements, many new features including features that can assist in improving performance.

The main focus in LAC365FO version 6.17 is:

• Performance
• Reliability 
• Usability (user-experience) and Flexibility
• Simplicity

Performance

• Time for the report execution has been optimized 
• Performance in Archive is optimized
• Query Wizard is much faster 
• Lower use of memory 
• New features in Query Wizard to assist in lowering size of XML-file
• Autoconversion of subreports into Query structure    

Reliability

• Automatic backup (option to schedule export)
• Compare functionality
• Auto update of Lasernet design (in case Output is restructed)

Usability and Flexibility

• Query Wizard
  • Improved search option 
  • Option to Copy, Move data-sources
  • Query links (master query) 
  • Better options for labels and language texts
  • Better options to structure the output (XML-file)
• Autoconversion of subreports into Query structure
• Autocreation of Design document

Simplicity

• Attachments (Attachments and entries from Archive)

Performance

Archive and option to reduce the size of the Archive

LAC365FO version 6.17 contains an option to reduce record-size in the Archive as this could become quite large.

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

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

Reliability

Backup / Scheduled backup

With the new version, you have the option to schedule the backup. This is to:

1. ensure a backup of the data exists
2. provide the option for automatically moving the reports across environments
3. re-import after restore

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

You can compress (ZIP) the backup - and you should. Because it's an XML file, you can compress it quite heavily.

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

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

Comparing Query definition and entries in the Archive

LAC365FO version 6.17 contains a new powerful option for comparing ’files’.

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

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

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

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

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

Compare queries

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

The feature is located in Lasernet > Common > Reports.

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

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

The following image is shown in case the definition for the queries are identical:

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

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

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

This would compare the two XML files within Archive:

Auto conversion of Lasernet design

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

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

Please ensure a backup is made of both the report-definition (Query) in LAC365FO and Lasernet design,  in case the conversion isn’t working as expected.

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

Example

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

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

2. Make an export of the report definition (Query) in LAC365FO and the Form in Lasernet (It's possible to Export multiple forms from Lasernet and import them into LAC365FO).

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

4. Run the report to identify patterns and rearranges that aren’t working as expected.

5. Import the Lasernet design into LAC365FO – Lasernet > Reports > Update design.

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

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

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

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

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

10. Click Deploy and then Patch.

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

Review and Document Handling

With this new release, you have the option to review before sending. This is highlt relevant, especially if you are in e.g. a test phase. Then instead of just delivering the document, you have an option to see the document and an option to see where it's going to be delivered - so you can basically test it.

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

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

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

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

The Pending review within the Archive would identify the document that hasn’t been delivered.

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

After the document is delivered through the Review

Usability and Flexibility

New options within the Query Wizard

Option to add report parameters into XML

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

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

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

Option to add labels directly within the Wizard

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

Layout: Option to “flatter” the output (Min, Medium, Max)

This feature lower the size of the file quite a lot - and indirectly increase the performance.

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

Maximum: contains data source name plus Detail_Collection and Details for each record
Medium: has only data source name and Details for each record
Minimum: just has data source name for each record

This is extremely useful when there is a need to optimize performance as it can lower the size of the XML file by using Minimum instead of Maximum. E.g. the file size when running report containing 1000 order lines would be 3.482 KB with Maximum in the structure versus 2.245 KB with Minimum in the structure.

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

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

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

The default when creating a replacement report is Maximum.

New search options – Across or for specific table

Searching for field names now contains two options:

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

This new feature is great, because instead of getting shown 25 tables, you can now select a specific table to search for the e.g. SalesID.

These new search options apply to the following areas:

• When adding fields
• When adding sort fields 
• When adding field(s) for a range

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

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

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

Copy/move of data-sources / table

The new version provides the option to copy or move the datasource(s), plus the option to include all nested data sources.

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

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

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

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

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

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

Improved label control with new option for labels (Top, Each, First, Hide) 

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

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

EachDataSourceNode: Shows labels at each of the nodes for a data source
FirstDataSourceNode: Show labels at the first node of each data source
Hide: Doesn't show any labels for the data source
Top: Show all labels at the top

EachDataSourceNode

FirstDataSourceNode

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

The following example illustrates the differences between EachDataSourceNode and FirstDataSourceNode.

EachDataSourceNode

FirstDataSourceNode

The following Query was used for the illustration above:

Hide

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

Top 

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

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

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

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

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

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

Copy/Link Query

This new feature provides the option to either copy or link to another Query. Query links, which is similar to sub-report, is useful if you have the same output across reports. Then you only need to maintain one report and it will reflect the packing slip, confirmation, account statement etc. You just do it once, and reuse it. Using a link to a Query provides the option to maintain and use one central Query – like a Query for the CompanyInfo.

The performance is also greater compared to using a subreport.

It's also possible to use a linked Query at detail/line levels containing information about item dimensions which could get re-used across multiple reports.

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

(Auto converting Subreport into Query)

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

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

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

Auto conversion of subreport(s) into Query

Here is an example of the new feature:

Imagine a Query that contains the following Company information:

This query is used as a subreport:

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

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

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

Auto-creation of documentation (FDD)

LAC365FO version 6.17 contains a powerful option for creating a design document (FDD - Functional Design Document).

The FDD is a design document to ensure that the customer requirements are met. It also includes a list of what needs to be done.

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

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

Select the required report followed by Generate report summary.

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

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

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

Simplicity

Simplified use of attachments

With the Lasernet Connector, you can add attachements at any records at any forms, you can add your product pictures, images, general terms and conditions etc. But now there has been added two additional options: Attachments from and attach.

Previously, it wasn't easy to work with, if you were working with the details with the sales lines. Therefore, working with attachments has been improved and now supports adding attachments at the line/detail level and now doesn't require the use of context methods.

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

Attachment from

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

This also works with attachments located at line level/details and therefore no need as in previous versions of LAC365FO to add a context-method.

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

From attachments

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

Reserved

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

Attach

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

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

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

Test & Performance Suite

Option to multiplying lines when replicate test data

• Useful when having the need for benchmarking performance
• Especially useful when a need to test with many records (high load)

Option to apply a description to the ‘Performance review’ (minor but useful)

• Useful for identifying the test-combinations

Option for running the std. Performance-Test within a batch-task

• Useful in case of a requirement to identify slow performance when running in batch

The Lasernet Connector for Finance and Operations roadmap 2022 is here!

Release date: 12-01-2022

We are pleased to announce that the latest roadmap for the Lasernet Connector for the FO product is now available to download.

2022 will be with a focus on new features, improvements and support for the FO Connector.

Click on the roadmap to download it and see what 2022 has to offer.

Please note: The roadmap is only indicative and is subject to change.

Release for the Lasernet D365 Connector
for Finance and Operations version 6.16.0

Release date: 06-10-2021

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

There are major enhancements in the LAC365FO version 6.16.0. This fall you can achieve:

• Improved performance
• Improved performance when using OData (data from D365CE)
• Improved usability and user experience

This is provided through the following major enhancements in LAC365FO version 6.16:

• Option to limit use of memory 
• Minimizing record-size for the report-definition
• Performance improvement in relation to OData-request(s)
• Improved Task-recording when using Test & Performance Suite (T&P)
• Better option to measure report-execution with Test & Performance Suite (T&P)
• New HTML editor/designer

Performance / Option to limit use of memory (Cache/memory)

LAC365FO version 6.16 contains an option to disable the saving of records in memory (cache of the records). 

The previous version of LAC365FO  always saved records in memory.

The advantage of saving records in memory is information/fields are retrieved faster if there’s a need to re-use information (tables/fields).

The disadvantage is the consumption of memory which could get reduced by disabling the cache.

It takes time (not a lot) to save record(s) in memory and in some scenarios possible to gain better performance by disabling cache – especially if a low number of fields are re-used.

(such as when most of the information (tables/fields) are added through the Query Wizard).

Re-using fields is an example when adding fields within the structure/elements or when re-using information for the file-naming.

Manually added information is colored “Yellow” within the elements – such as the following:

The best practice is to add as much as possible through the Query-Wizard and avoid as many yellow elements as possible.

“Yellow elements” could end up harming performance for the Report and the overall performance.

Adding as much as possible through the Query-Wizard would also ensure a minimum of roundtrips to the database which especially is important when having ”higher” latency and/or ”low” bandwidth.

Some tests are needed to identify the best/optimal performance settings of the cache.

The option to disable cache is located at Report-level – Lasernet > Common > Reports.

Cache-control

• Default (Defined within the Lasernet parameters)
• Use cache. Save record(s) in memory both when running report(s) in batch and through UI
• Disable cache. Never save record(s) in memory.
• Disable cache in batch

Save record(s) in memory when running the report(s) from UI but not when running through a batch-task.

The module Test & Performance Suite is a great tool for identifying the best settings in relation to performance as it contains the option for logging the following information:

• Average execution time for report
• Average execution time for report - Including time for the batch-task
• Memory usage (%) for report
• CPU usage (%) for report

Execution time, Memory usage and consumption of the CPU.

The Idea of using the Test & Performance Suite is to execute like 10/100/1000 reports within a batch task and identify the best settings.

Disable cache in the batch is useful in case there’s a need to lower memory usage when running batch tasks, such as when posting and printing invoices.

Performance / Limit size of report-definition

The record containing the report-definition/structure is optimized to a minimum size.

Implemented by moving the Stylesheets (Transformation Stylesheet, Sorting Sylesheet) into a new table as the sizes of the stylesheets often can get quite big.

Having Stylesheets within a separate table ensures they only are loaded when needed.

Moving Stylesheet from existing to new table happens when the record containing the report definition gets updated (Table=LACReport)  – Like when Saving, Importing or modifying a Report.

Technical

Existing table containing the report-definition

Tablename: LACReport

New table containing the Stylesheets in which the Stylesheets are moved into

TableName: LACReportStyleSheets

                  SortStyleSheet

                  TransformStyleSheet

Possible to move Stylesheets back from LACReportStyleSheets into LACReport by adding the following to the URL.

Remember to use the right legal entity/company, such as &cmp=USMF in the following:

 https://<server>/?mi=SysClassRunner&prt=initial&cls=LACReportStyleSheetMover&cmp=USMF

This would move the Stylesheets for all reports from the table LACReportStyleSheets back to the table LACReport.

Approach to identify best performance settings by using T&P

The module Test & Performance suite (T&P) is a separate module and requires an additional license key to get activated.

It’s possible to obtain a demo license for trial purposes.

The following approach is required for all reports as each report could have a different structure and behavior. 

Most important for reports which are critical in relation to performance such as the packingslips as an example.

But similar approach for reports having Long execution time, High memory usage and/or High consumption of CPU.

Run x-number of reports by using the following approach, such as 10/100/1000 reports.

1. Start by enabling Cache for the Report – Lasernet > Common > Reports.

2. Run a number of reports – like 10/100/1000 reports.

A. Open Batch print schedule (Top picking) which is located in Lasernet > Test & performance suite > Performance > Batch print schedule (Top picking)

B. Start by selecting the required Report before entering the destination.

(Report is required for selecting a proper destination)

Enter a dummy destination like Fax ’1234’ – like the following:

C. Enable Run in batch and set the Number of tasks/threads (Like 4/8).

D. Enable Log per report, Log CPU and Log memory usage and set Log performance on every ’x’ report to 1.

Open review form would ensure the Form containing the logging information automatically are opened.

It is possible to open same Form from Lasernet > Test & Performance suite > Performance > Batch print review.

E. ”Check” the logging in relation to Execution time, Memory Usage %, CPU Usage % in the Form Batch print review

D. Disable the cache at report level.

3. Repeat Step 2 and re-run x number of reports – like 10/100/1000 reports.

4. Check the logging and compare with the previous logging in which cache was enabled (step 2.D).

It’s also possible to use the Tracking/Performance indicators to identify the best settings for a report.

It is important to run the same report multiple times as it’s caching the report definition and query the first time the report is executed.

Lasernet > Setup > Parameters > Performance

Example on processing report which contains yellow elements 

Cache enabled vs. cache disabled

New HTML Editor/designer

It’s in LAC365FO version 6.16 possible to activate the new HTML editor control which is introduced as a preview feature in standard D365FO.

It's still possible to select and use the Legacy HTML editor or Plain text.

The options are available in Lasernet > Setup > Parameters > Email.

Selecting the new HTML editor should get shown as the following:

Please ensure the New HTML editor control is enabled within the Feature management in standard D365FO in case it isn’t shown as above.

It's still possible to use the old editor by selecting Legacy HTML editor within the Lasernet parameters. The old/ Legacy HTML editor is also used as a”fallback” in case the New HTML Editor doesn’t exist or isn’t enabled.

Legacy HTML-editor

Working with images within the new HTML Editor

Images are added by using the Select image file.

Afterward, select the required file which contains the Image.

The added image will get previewed and added into Mail-body (HTML).

Adding an image within the new HTML editor would add the image into the image table in LAC365FO.

Image table in LAC365FO– Lasernet > Setup > Lists > Images

It’s possible to use an image added to the image table in both the HTML editor and within the Report group in LAC365FO.

The image is added into the MailBodyHTML when running the report (Base64 Encoded).

Please be aware exporting a report(s) using the Legacy HTML editor into the new HTML editor would require some adjustments in relation to the images which have been added.

TEST & Performance Suite

The Test & Performance Suite module contains the following enhancements:

• Improved use of Task-recording 
• Better option to measure report-execution

Improved use of Task-recording

Using the Task-recorder with the UX testing (User Experience) is improved and now contains an option for adding add a pause.

UX-testing

The task-recorder used with the Test & Performance suite is a powerful tool for recording processes and is used in T&P to identify if a process succeeds or fails.

Having a task-recording in which a destination was selected could hang once it was used with the UX-testing.

This is improved in LAC365FO version 6.16.

Task recording contains the execution of a document:

The following would hang in previous versions of LAC365FO:

Improvement when using batch testing

Additional information regarding execution time is added into the Batch print review and is useful when tracking bottlenecks in relation to Execution-time, performance, Memory/ CPU usage.

Time per report (without batch overhead) contains the average execution time without any overhead caused by the batch/batch-task.

Please have in mind that the value for Time per report (without batch overhead) could get higher compared to  Time per report (ms) in case ”multi-threading” are used (multi tasks/threads).

Example when using 4 tasks/threads

Multi-threading would cause Time per report (without batch overhead) to get higher compared to Time per report (ms).

Single-threading (single task) would cause almost identical numbers:

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

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

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

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

New model LasernetPU35Spec

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

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

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

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

Lasernet > Setup > Parameters

Add the AOT-package:

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

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

Major enhancements 

Lasernet 10 

LAC365FO version 6.15 does not contain any major adjustments and focus is still on stability and compatibility and a new Default Configuration for Lasernet 10 is released at the same time as LAC365FO version 6.15. 

The new Default Configuration also works with the previous versions of LAC365FO version 6.x and LAC365FO version 6.15 isn’t required for supporting Lasernet 10 as all adjustments are managed within the Lasernet configuration. 

The new Default Configuration support loading of the following information from Lasernet 10:

(same information as was supported with Lasernet 9) 

• Lookup of connections in LAC365FO 

• Get printers into LAC365FO version 6.x 

• Get printer profiles into LAC365FO version 6.x 

• Get ‘Customers ports’ into LAC365FO version 6.x 

• Get overlays into LAC365FO version 6.x 

• Preview of overlays in LAC365FO version 6.x 

It’s currently not possible to get the printer profiles created through the new Lasernet Print Service which was introduced with Lasernet 10.  But still possible to get Printer profiles created for the module Printer Output (OnPrem) in Lasernet 10, similar to  Lasernet 9. 

It is possible to load the Printer profiles created for the module Printer Output. 

The required adjustments to the Lasernet configuration to support Lasernet 10 are described at the end of this document (before the list of the Bug fixes and enhancements) 

Bug fixes and enhancements 

227499@LAC365FO – Print Button on Lasernet Preview Screen does not result in printing 

Printing through Lasernet within the preview didn’t work as expected. 

This is fixed in LAC365FO version 6.15.0 in which Print through the preview is now working as expected. 

223936@LAC365FO – Range is being applied to nextLink URL, which already contains range. 

 The following error was thrown when running an OData report which contains a range added within the Query Wizard. 

This is fixed in LAC365FO version 6.15.0. 

227317@LAC365FO – Table LACReportReplacementMapping is in Table group Miscellaneous 

It was not possible in previous versions of LAC365FO to use the following tables in the cross-company data sharing in standard D365FO.  The tables had Miscellaneous as a table group which caused the issue in relation to the cross-company data sharing:

• LACReportReplacementMapping 

• LACCultureInfo 

• LACExpressionFunction 

• LACMenuTable 

• LACReportGroupReport 

• LACWHSLicensePlateLabelRef 

• LACWHSLicensePlateLabelSetup 

228645@LAC365FO – Data missing in XML 

Re-using the same table multiple times within a Query would cause an empty output when disabling the first use of the table. The issue is caused as standard D365FO (kernel) tries to optimize the Query and would skip all instances of a table once it has been disabled. 

 A workaround was removing the disabled data sources. This would avoid the kernel optimizing the Query and avoid executing the disabled data sources. This is fixed in LAC365FO version 6.15 by not applying the disabled data sources (tables) when building the Query at runtime. 

228681@LAC365FO – Form link condition does not work on replacement reports, but work on query reports 

In previous versions of LAC365FO,  it was not possible to use Form as an entry within the condition (expression). 

LAC365FO version 6.15 does support the use of Form as an entry for the expression.

224895@LAC365FO – Check loading of printer-profiles 

Loading printer profiles from Lasernet would add the same printer profiles to all the printers and not only the printers in Lasernet containing the profiles. 

This was only an issue when loading from the Form Printer profiles and everything did work as expected when loading from the forms Lasernet server or Lasernet printers.

229365@LAC365FO – Feature Request: Translation of Lasernet Print Destinations 

The Lasernet-destinations were not properly translated for some of the languages within the printer-dialog, such as Spanish (es). 

Translation is added for the following languages within the Printer-dialog:

• Es 

• Nl 

• de-CH 

• fr-CH 

• fr 

• de 

230415@LAC365FO – Lasernet Query is rounding values in XML when selecting more than one documents to print 

Multi-selection of records could cause an issue with the formatting of the output. (like which numbers are shown / rounding). 

This is fixed in LAC365FO version 6.15.0.

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

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

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

LAC365FO version 6.14.0 contains the following models/packages:

• Lasernet: core and main engine for LAC365FO
• Lasernet81Spec: Additional requirements in relation to 8.1 and newer versions of standard D365FO
• PRNButtons: Lasernet print buttons
• PRNButtonsLACAdaptor: Adaptor between the Lasernet print buttons and Lasernet
• LACCE: Provide the integration to CE from LAC365FO
• LACMSHotfixes: Hotfixes for standard D365FO
• Lasernet Test Suite: Test & Performance Suite

New model LasernetPU35Spec

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

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

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

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

Major enhancements

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

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

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

Stability

Support for PU43 (10.0.19)

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

LAC365FO contains the new option Auto detect patterns.

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

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

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

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

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

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

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

Optimized form links

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

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

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

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

Usability / Simplicity

Adding images/pictures

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

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

• Lasernet > Setup > Lists > Images

• Lasernet > Common > Reports

• Lasernet > Setup > Lists > Report group

Lasernet > Setup > Lists > Images

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

Lasernet > Common > Reports

Images are added specifically for the report.

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

Lasernet > Setup > Lists > Report group

Provides the option to add images across a number of reports.
Images are added (binary encoded) into the XML file.
They can get used in Lasernet by using Image > Job > Base64.

Bug fixes and Enhancements in LAC365:

• 220677@LAC365FO – Query version (QueryWizard vs FormLinks vs Last Value) miss-match produces various unpredicted results.
• 220934@LAC365FO – Check report query Last values affect between multiple Form links and Dialog defaults.
  A version of the Query is no longer saved within the Form links.
  This approach is used to ensure existing ranges are kept for the Query within the Form links after modifying the Query within the Query Wizard.
• 220765@LAC365FO – Validate enum value on the parameter.
  A warning is displayed in LAC365FO version 6.14.0 when entering a non-existing value for an Enum.
  Note: It was possible in previous versions of LAC365FO to enter a non-existing value for the Enum.
• 220766@LAC365FO – Batch execution does not have LACReport initialized when running CE(class) reports.
  In previous versions of LAC365FO, it was not possible to execute an OData report within a batch task.
  LAC365FO version 6.14.0 supports the option to use a batch-task for an OData-Query (CE).
  Executing an OData-Query (CE) within a batch task would throw the following error: 'Batch task failed: Object reference not set to an instance of an object.'
• 220807@LAC365FO – Unable to lookup ODATA field values, when field property is different from field name.
  Making a lookup of OData fields didn’t work as expected when the field property was different from the field name - such as having a field-entity accountId for the entity quotes.
  This is fixed in LAC365FO version 6.14.0.
• 220971@LAC365FO – Adding custom(yellow) OData field is not initializing right data type, as fields are taken only from selected fields in the wizard.
  The Type/Datatype when adding an element manually for an OData-Query wasn’t set to the proper type, such as in the following in which the Type/Datatype should become a Real.
  Only an issue when using an OData-Query and work-around was manually adjusting the Type/Datatype.
  The Type/Datatype are set properly in LAC365FO version 6.14.0.

• 221048@LAC365FO – Lookup of SharePoint subsites is limited to 99
• 220160@LAC365FO
  Previous versions of LAC365FO did only support lookup for 99 subsites when using Sharepoint within the connection for a server.
  LAC365FO version 6.14.0 supports an “unlimited” number of subsites.
• 221103@LAC365FO – Image list for Lasernet reports
  A new option for adding images like the company logo is added into LAC365FO version 6.14.0.
  It’s possible to add the pictures/images at the following locations:       
  • Lasernet > Setup > Lists > Images
  • Lasernet > Common > Reports
  • Lasernet > Setup > Lists > Report group
• 221384@LAC365FO – Validation on orphaned LACReportParameters
  Activating the following preview feature could cause issues when saving the record at a Form.
  It could also cause issues when trying to add a condition to the Form.
  The Work-around was disabling the following preview feature in std. Dynamics 365 for Finance & Operation.
• 221459@LAC365FO – EcoResProductCategory somehow is referenced in Retail and in PU43 requires Lasernet reference to Retail.
  A reference to the model Retail is required for the model Lasernet when using Dynamics for Finance & Operations PU43 / 10.0.19.
  This is added in LAC365FO version 6.14.0.
• 221478@LAC365FO – Error on validation of report type class.
  Validating a report of type Class (OData/CE) could throw an object reference error. Refreshing the meta-data could avoid this error.
  This is fixed in LAC365FO version 6.14.0.
• 221538@LAC365FO – Validation on License expiration fails on older kernels (PU3)
  The following warning was displayed when opening either the Form Lasernet reports, Lasernet parameters or when processing a report and when having an expiration date for the license. The warning was shown even though the Expiration warning was set as low as it shouldn’t throw the warning. – such as when using an open demo license having an Expiration date.
  This is fixed in LAC365FO version 6.14.0.
• 221912@LAC365FO – Empty screen after review and after applying a signature to a document.
  An empty screen was shown after delivering a document for which a signature was added within the review of the document.
  This is fixed in LAC365FO version 6.14.0 and no empty screen is shown after delivering a document containing a signature.

Bug fixes and Enhancements in LAC365:

• 214839@LAC365FO Range locking from wizard
• 214868@LAC365FO Reset of the ranges removes all ranges for an OData Query/Report
• 214972@LAC365FO Context form data source field range not initialized
• 215062@LAC365FO Odata relations only supports immediate parent
• 215063@LAC365FO Archive is enabled, even if there are no archives (Test suite related)
• 215196@LAC365FO Resend/Lasernet Original preview changes selection when clicked
• 215366@LAC365FO Issue with language ID on replacement/groupedBy/TempDB report
• 217598@LAC365FO Image padding fix on added Lasernet menu item
• 215698@LAC365FO Reset query ranges removes "Show" values for ranges
• 215799@LAC365FO Bad request when trying to run some class reports containing referential relationships.
• 215914@LAC365FO Feature Request - Lasernet Connector - Remove all Fields: Provide popup
• 215915@LAC365FO T&P: Label translations needed (de, en-gb, en-us, da)
• 215975@LAC365FO Mapping fields isn't properly filled when using the background print (T&P)

• 216532@LAC365FO Version label was not updated in all languages
• 216535@LAC365FO Query definition download, for query compare and etc.
• 216627@LAC365FO ReviewPending should always have the value 'No' when using preview/screen as destination
• 216815@LAC365FO Line breaks preservation in XML attributes
• 217086@LAC365FO Email editor is not working on some environments (option to disable HTML-editor and use flat text)
• 216758@LAC365FO Report > Form link > "Single button" option for the Replacement
• 216815@LAC365FO Line breaks preservation in XML attributes
• 217401@LAC365FO Report shows that has fixed report, where actually it does not. Other small issues
• 217598@LAC365FO Image padding fix on added Lasernet menu item
• 217860@LAC365FO Problem with Enum labels in ranges
• 217862@LAC365FO Move, copy or Process Archive Lifespan for documents created in LAC V5
• 217900@LAC365FO .Net dateTime compare crashes AOS on license check (only old kernels)
• 218098@LAC365FO Reset ranges doubles up the ranges
• 218122@LAC365FO When report parameter is set to range - replace on lookup should be set to false
• 218271@LAC365FO Expression lookup filtering when lookup is open

Bug fixes and Enhancements in LAC365:

• 205965@LAC365FO Issue when using dialog-fields for the report-range/filter
• 206145@LAC365FO Width, Height and Pen-size isn't saved when adjusted in Review
• 206158@LAC365FO Using Form-adjustment cause hide/wrong placement of the buttons
• 206234@LAC365FO Subreport query is not refreshed on each line, causing OR ranges, and wrong results
• 207150@LAC365FO Option to disable cache for a query/table
• 207378@LAC365FO Change default CPC Polling interval for Azure storage from 15 to 5 seconds.
• 207731@LAC365FO getRelatedRecord() issues when empty record or sibling data source
• 207803@LAC365FO Overlay validation fails - The expected type was str, but the encountered type was int.

• 207826@LAC365FO Display how many printers were inserted, updated or deleted when downloading CPC printers
• 208113@LAC365FO Print buttons initialized twice when opening Sales quotation send quotation form
• 208177@LAC365FO LAC365FO version 5 and LAC365FO version 6 - Entering same number/characters doesn't work within the expression
• 208273@LAC365FO View LACLogisticsPostalAddressViewNoValidDate returns %1 in Address field instead Country translation
• 208628@LAC365FO Number of decimals isn't always added properly when added through the Query Wizard
• 208950@LAC365FO One click: available reports must be active
• 208967@LAC365FO Remove scroll-bar within the Query-Wizard for the properties
• 208974@LAC365FO Only active reports when Show related reports are unmarked
• 209083@LAC365FO Issue to use Default ranges for a class-report Dyn 365 v.10 PU24 and up