Version 6.1.0 is now available for all users.
This release introduces Liquibase as the new upgrade mechanism for database schema migrations. By replacing the previous manual SQL upgrade scripts, Liquibase enables structured and traceable schema changes, provides a dedicated execution history via the databasechangelog table, and ensures more consistent upgrades across different database systems.
In addition, the revision ID data type has been updated from INT to BIGINT in the RS_REVISION table and all _A tables. This change allows the system to support significantly larger data sets in environments with extensive revision histories.
ReportServer 6.1.0 also includes several bug fixes and usability improvements, including a fix for the Saiku and Pivot “Drillthrough as CSV” export, as well as improvements to the JVM Live Memory and ConnectionPool views, where previously non-functional controls have been corrected and UI elements adjusted for greater consistency.
For a list of all changes please refer to the Release Notes. The upgrade guide is available in the documentation area.
Happy reporting!
Version 6.1.1 is now available for all users. This release focuses on important bug fixes and stability improvements.
Multi-level cascading parameters now correctly retain their saved values when reopening report variants. The table display in report view has also been improved, resolving issues with shrinking columns and enabling proper resizing.
In addition, quick export has been fixed to handle previously unresolved references (e.g. TeamSpace reports and user variables), and a packaging issue causing duplicate Liquibase changelog files—preventing startup in some cases—has been resolved.
For a list of all changes please refer to the Release Notes. The upgrade guide is available in the documentation area.
Happy reporting!
Version 6.1.2 is now available for all users. is now available for all users. This release includes a small hotfix to improve usability in table report previews.
Auto-Fit is no longer always enabled in table report previews. For reports with many columns, AutoFit is now automatically disabled, improving readability and preventing columns from becoming too narrow.
This is a temporary solution and will be replaced by a configurable approach in a future release.
For a list of all changes please refer to the Release Notes. The upgrade guide is available in the documentation area.
Happy reporting!
ReportServer 6.1.3 released
Version 6.1.3 is now available for all users. This maintenance release focuses on stability, usability, and improved permission handling.
The most important change introduces enforced unique user variable names. User variable names are now validated in the administration UI and are also protected by a database constraint. During the upgrade, existing duplicate, empty, or missing user variable names are automatically renamed to allow the migration to complete successfully. Administrators should review these automatically generated names after the upgrade and update affected reports where necessary.
Another important improvement fixes a scheduling issue where users could be prevented from creating or editing schedules because of permission checks on unrelated report conditions. The scheduling wizard now evaluates only report conditions that are applicable to the report being scheduled, preventing unnecessary permission-related failures.
In addition, this release fixes the visibility of the “Remove” buttons in the dynamic list filter dialog and resolves an issue in the TeamSpace history tab where an exception could occur if no revisions were available.
For a full list of changes, please refer to the Release Notes. The upgrade guide is available in the documentation area.
Version 6.1.4 is now available for all users.
This maintenance release focuses on stability and resolves a regression introduced in version 6.1.3.
The most important fix addresses a startup issue affecting new ReportServer installations. During the initial startup, Liquibase could incorrectly execute database upgrade migrations even though the database schema had already been created from the provided DDL scripts, causing the startup to fail. ReportServer now correctly detects fresh installations and synchronizes the Liquibase changelog with the existing schema instead.
This regression only affected new installations. Existing ReportServer installations upgrading from an earlier version were not affected.
For a full list of changes, please refer to the Release Notes. The upgrade guide is available in the documentation area.