Release Notes for ReportServer 3.7.0

These release notes reflect the changes with respect to ReportServer 3.6.0.

• Some Important Features and Noteworthy Improvements
• Support Sending Reports to Email - SMTP Server Datasinks
• Support Sending Reports to OAuth-Authenticated Datasinks
• Support Sending Reports to OneDrive - SharePoint (O365) Datasinks
• Support Sending Reports to Dropbox Datasinks
• New Features, Improvements and Bug Fixes for RS3.7.0-6043
• New Features, Improvements and Bug Fixes for RS3.7.0-6044

Some Important Features and Noteworthy Improvements for ReportServer RS3.7.0

Support Sending Reports to Email - SMTP Server Datasinks

Email SMTP datasinks allow to send/schedule reports to a given SMTP server. Email - SMTP datasink configuration can be made in the Administration area. Permissions to Email - SMTP datasinks can be given analogously as to other objects in ReportServer.

You can set a default email datasink in the datasinks.cf configuration file. This replaces the old mail.cf file.

Email SMTP datasinks email text configuration is done in the /fileserver/etc/scheduler/scheduler.cf file, available in the Configuration guide.

Note that the old /fileserver/etc/mail/mail.cf configuration file is deprecated. You can use email SMTP datasinks together with the default email datasink setting instead.

Email - SMTP datasink configuration is done in the /fileserver/etc/datasinks/datasinks.cf configuration file, available in the Configuration guide.

Support Sending Reports to OAuth-Authenticated Datasinks

OAuth2-authenticated datasinks use, as their name suggest, OAuth2 https://oauth.net/2/, the industry-standard protocol for authorization.

Before being able to use oauth2-datasinks, you have to create an app in the service needed and authorize file uploads in this app. You can then add your app key and app secret into the respective ReportServer fields and save the datasink.

When this is achieved, you can click the “Datasink OAuth2 Authentication Setup”, which redirects you to the service authorization. Please note that you have to add the “redirect URI” into your app. This redirect URI is shown when clicking the before-mentioned button. The URI should be similar as this: http://localhost/ReportServer/reportserver/oauth. When this is done, after app authorization and automatic redirection, you should be able to use your oauth2-datasinks. For testing your datasink, as with other ReportServer datasinks, you can use the “Test datasink” button.

Support Sending Reports to OneDrive - SharePoint (O365) Datasinks

OneDrive - SharePoint (O365) OAuth2-authorized datasinks allow you to send and/or schedule reports to a given directory in your OneDrive - SharePoint (O365) http://onedrive.com/ account. Note that OneDrive for Business is also supported (Office 365), as well as SharePoint O365. Older SharePoint versions are currently not supported.

For getting your “app key” and “secret key”, you have to create an app registration here: https://portal.azure.com/ (Azure Active Directory - App registrations section) and give it the appropriate API permissions (API permissions section). Specifically, files.readwrite.all is needed. The secret key can be created in the “Certificates and secrets” section. More information on this can be found here: https://docs.microsoft.com/en-us/graph/auth-register-app-v2. Note that when permissions are changed, it is necessary to create a new “refresh token” with the “Datasink OAuth Authentication Setup” button.

The “base root” path in the datasink definition, together with the “folder” path, determines the base path of the datasink. The default folder/folders are also included, which can be overriden in specific uses of this datasink, analogously to other datasink types.

If needed, you can configure your tenant id, available in your Microsoft account. You can use the default if this is not needed or if you don’t have a custom tenant id.

Support Sending Reports to Dropbox Datasinks

Dropbox OAuth2-authorized datasinks allow you to send and/or schedule reports to a given directory in your Dropbox https://www.dropbox.com/ account. Note that Dropbox for Business is also supported: https://www.dropbox.com/business/.

The path in the datasink definition determines the base path of the datasink. It also contains a default folder/default folders, which can be overriden in specific uses of this datasink, analogously to other datasink types.

Note that the base path must exist. If the (extension) folder/folders does/do not exist, it/they is/are created. If the report already exists in the same path, it is overwritten. The path should be given like this: /my/path. Note that, different as in other datasinks, ./my/path does not work.

New Features, Improvements and Bug Fixes for ReportServer RS3.7.0-6043

New Features, Improvements and Bug Fixes for ReportServer RS3.7.0-6044