ReportServer 3.1.0 BETA release

Dear ReportServer users,

we are happy to release the BETA Version of ReportServer 3.1.0. You can download it from here:  Reportserver Download

We made numerous improvements / changes. The complete list can be found here: Docs

The most important changes that are relevant for testing are:

– RS-3576    New Feature     – Upgrade to POI 4.1.0Upgrade to POI 4.1.0 -> Test if the Excel Export of your Reports works fine
– RS-3579    New Feature     – Support JXLS2 reports -> Test if your JXLS 1 reports / templates for the dynamic list work fine
– RS-3588    New Feature     – Upgrade to BIRT 4.8.0 -> Test if your BIRT reports work fine.
– RS-3592    New Feature –  Upgrade to Jasper 6.9.0 -> Test if your JASPER reports work fine.
– Improvement    Combine offset and order queries in MySQL / MsSQL / PostgreSQL / Oracle dynamic list reports -> Test your dynamic lists

Please let us know if you have any problems with the BETA version, especially if some report was working in 3.0.8 but is not working correctly in 3.1.0-BETA. Of course, as this is a BETA version, it should not be installed in production environments. Always backup your data completely before installing the BETA release.

For testing, just unzip it into the webapps directory of your Tomcat installation. As always, you need to set the persistence.properties file and run the corresponding DDLs. As always, please restart your tomcat and delete your browser’s cache including temp files.

If you are upgrading from a previous installation, you first need ReportServer 3.0.8 correctly installed. Then, just run manually the following SQL script:
After running the script, please restart your tomcat and delete your browser’s cache including temp files.

MySQL 5:

ALTER TABLE RS_JXLS_REPORT ADD jxls_one BIT(1);
ALTER TABLE RS_JXLS_REPORT_A ADD jxls_one BIT(1);

UPDATE RS_JXLS_REPORT SET jxls_one = 1;

ALTER TABLE RS_JXLS_REPORT MODIFY jxls_one BIT(1) NOT NULL;

INSERT INTO RS_SCHEMAINFO(KEY_FIELD, value) VALUES('updated', date_format(now(), '%Y-%m-%d %T'));
INSERT INTO RS_SCHEMAINFO(KEY_FIELD, value) VALUES('script', 'RS3.0-14-MySQL5_UPDATE');
INSERT INTO RS_SCHEMAINFO(KEY_FIELD, value) VALUES('schemaversion', 'RS3.0-14');

Oracle:

ALTER TABLE RS_JXLS_REPORT ADD jxls_one number(1,0);
ALTER TABLE RS_JXLS_REPORT_A ADD jxls_one number(1,0);

UPDATE RS_JXLS_REPORT SET jxls_one = 1;

ALTER TABLE RS_JXLS_REPORT MODIFY jxls_one number(1,0) NOT NULL;

INSERT INTO RS_SCHEMAINFO(ENTITY_ID, KEY_FIELD, value) VALUES((select max(i.ENTITY_ID)+1 ENTITY_ID from (select ENTITY_ID from RS_SCHEMAINFO union select 1 ENTITY_ID from dual)i), 'updated', to_char(sysdate, 'YYYY-MM-DD HH24:MI:SS'));
INSERT INTO RS_SCHEMAINFO(ENTITY_ID, KEY_FIELD, value) VALUES((select max(i.ENTITY_ID)+1 ENTITY_ID from (select ENTITY_ID from RS_SCHEMAINFO union select 1 ENTITY_ID from dual)i), 'script', 'RS3.0-14-Oracle_UPDATE');
INSERT INTO RS_SCHEMAINFO(ENTITY_ID, KEY_FIELD, value) VALUES((select max(i.ENTITY_ID)+1 ENTITY_ID from (select ENTITY_ID from RS_SCHEMAINFO union select 1 ENTITY_ID from dual)i), 'schemaversion', 'RS3.0-14');

PostgreSQL:

ALTER TABLE RS_JXLS_REPORT ADD COLUMN jxls_one boolean;
ALTER TABLE RS_JXLS_REPORT_A ADD COLUMN jxls_one boolean;

UPDATE RS_JXLS_REPORT SET jxls_one = true;

ALTER TABLE RS_JXLS_REPORT ALTER COLUMN jxls_one SET NOT NULL;

INSERT INTO RS_SCHEMAINFO(KEY_FIELD, value) VALUES('updated', to_char(now(), 'YYYY-MM-DD HH24:MI:SS'));
INSERT INTO RS_SCHEMAINFO(KEY_FIELD, value) VALUES('script', 'RS3.0-14-PostgreSQL_UPDATE');
INSERT INTO RS_SCHEMAINFO(KEY_FIELD, value) VALUES('schemaversion', 'RS3.0-14');

SQL Server:

ALTER TABLE RS_JXLS_REPORT ADD jxls_one bit;
ALTER TABLE RS_JXLS_REPORT_A ADD jxls_one bit;

UPDATE RS_JXLS_REPORT SET jxls_one = 1;

ALTER TABLE RS_JXLS_REPORT ALTER COLUMN jxls_one bit not null;

INSERT INTO RS_SCHEMAINFO(KEY_FIELD, value) VALUES('updated', format(getdate(), 'yyyy-MM-dd HH:mm:ss'));
INSERT INTO RS_SCHEMAINFO(KEY_FIELD, value) VALUES('script', 'RS3.0-14-SQLServer_UPDATE');
INSERT INTO RS_SCHEMAINFO(KEY_FIELD, value) VALUES('schemaversion', 'RS3.0-14');

We will be happy to get numerous feedback on the BETA version. For this purpose, we created this forum thread: https://forum.reportserver.net/viewtopic.php?id=1541

Best regards,

Your ReportServer Team

Teradata Support

ReportServer 3.1.0 will support Teradata databases!

Teradata is a fully scalable relational database management system produced by Teradata Corp. It is widely used to manage large data warehousing operations.

Of course, pivot reports for dynamic lists will support Teradata datasources because of the JDBC mechanisms of ReportServer!

Your ReportServer Team

Amazon Redshift

More good news! ReportServer 3.1.0 will support Amazon Redshift datasources!

Amazon Redshift is a fast, fully managed data warehouse that makes it simple and cost-effective to analyze all your data. It allows you to run complex analytic queries against petabytes of structured data.

Further, your beloved pivot reports for dynamic lists will support Amazon Redshift datasources because of the JDBC mechanisms of ReportServer!

Happy Reporting!

Your ReportServer Team

Google BigQuery

Exciting news ! ReportServer 3.1.0 will include support for Google BigQuery datasources!

Google BigQuery is a serverless, highly-scalable, and cost-effective cloud data warehouse with an in-memory BI Engine and machine learning built in.

Even your beloved pivot reports for dynamic lists will support BigQuery datasources, since these use the existing JDBC mechanisms of ReportServer!

Keep tuned and happy reporting!

Your ReportServer Team