Version 2025 R2 Release Notes

This module now supports connecting to alarm databases from multiple facilities or sites in the same project.

The connector for this module is streamlined so the settings you actually tune day-to-day are front and center, while rarely changed “secondary” options are tucked away to reduce clutter. Wherever possible, table-driven choices (like columns and filter values) are now presented for selection, so users can pick valid options instead of manually typing syntax-specific values.

Data connectors for the module are now modular giving you the flexibility to connect different subreport groups in different locations in a report template.

Couple this with the ability to report from multiple facilities and now, in a single report, metrics can be displayed from multiple facilities for comparison purposes.

Added support for MariaDB databases.

When adding a new Database connector, the specific database type selected is now the default when you define the connection to that database.

Multiple Site Support

The Ignition Historical Values connector is updated to support a specific Gateway to ensure the proper data is returned for each tag.

The tag browser for the Ignition Historical Values provides a hierarchical view for the tags. For the Gateway, each Provider is shown, then the tags specific to that provider. Tags are displayed with the Provider name.

Note to current users with Ignition Historical Values connectors, when the project is opened, the connector is updated to the first Gateway configured in Ignition. All tags are updated to have the Provider displayed. If this cannot be determined, the tag is marked as static text and will need to be resolved manually.

MariaDB Support

Added support for Tag Historian configured to log to MariaDB.

When connecting to the FactoryTalk Historian SE using the new FactoryTalk DataAgent (version 5.0), a filter can be used to hone in on specific tags in the historian. This filter allows you to get past the 2,000 tag limit seen with earlier versions of the FactoryTalk DataAgent (version 4.0 and below).

This is a new connector to report on data from the Canary Labs Historian via the READ API.

Corrected an issue if the Identity is set up as Custom account, after specifying the Account, Password and Confirm, the Setup button would not be enabled.

Note that this dialog is accessible after installation from the System Check application by selecting Tools, Set up Web Portal.

Corrected issue where if Tag Historian is configured to log to PostgreSQL, when a data group is run, a SQL error would appear for the sqlth_partitions table.

Corrected issue where if the web portal was set up to any port other than the standard http port (port 80), the Web Portal button would not load the web portal in the default web browser of the system.

Corrected issue where if Windows date format is changed after installing XLReporter Distributed Edition, when opening the Project Explorer, an error about converting a date in the original date format would pop up.

Data Management

Corrected issue where, if File Versioning is enabled in the project and in a template data management is saved, an error would pop up complaining about the user account.

Data Group Builder

Corrected issue where, if File Versioning is enabled in the project and a data group is saved in the Data Group Builder an error would pop up about component licensing.

Schedule Designer (from Template Studio)

Corrected issue where, if File Versioning is enabled and schedule is modified and saved from the Schedule Designer accessed from within the Template Studio, a reason is not prompted from the user for versioning/auditing purposes.

Corrected issue where if the Workbook Report Name is empty, if the report is ran on demand, the data is populated directly in the template. Now, the report name is assumed to be the same as the template so a report is created named the same as the template and written to there, keeping the template data free. Note that in later versions of XLReporter, the Workbook Report Name cannot be left blank, this would have resulted in an upgrade from an older version of XLReporter.

Corrected issue with certain parameter dialogs where if the dialog is closed by clicking the “X” in the top right corner, it would cause the entire Data Manage to close and return to the worksheet. If the Data Manage option is selected again, it would not open. Seen with the following Functions/Parameters: