Deprecation of Custom Reports with the February '21 Release
Note: This deprecation was first announced as part of the May '20 release.
Cornerstone will be deprecating the legacy reporting solution "Custom Reports" with the February ’21 Release. With Reporting 2.0, users can execute the same business reporting operations as they've done in Custom Reports in addition to Reporting 2.0's rich suite of new features and functionality.
Standard reports will eventually be deprecated, but the timeline has not been determined.
For more detailed information about Reporting 2.0, see the following in Online Help:
- See Reporting 2.0 Overview.
- See Reporting 2.0 - Create Report.
- See Reporting 2.0 - Share Report.
- See Reporting 2.0 - Report Delivery and Scheduling.
- See Reporting 2.0 - System Templates.
Custom Reports Auto-Migration with February '21 Release
When the deprecation occurs, existing Reports will be migrated automatically to Reporting 2.0. For clients that have already done the migration themselves and/or who no longer need the custom reports, there will be an option to opt out of being migrated.
Clients who wish to migrate their custom reports into Reporting 2.0 ahead of the February ’21 deprecation can do so by using the custom reports migration tool available in Reporting 2.0. Report properties and certain configurations are preserved in the migration, such as shared users and delivery settings. However, some configurations may need to be manually enabled. See Reporting 2.0 - Custom Reports Migration Tool.
Upon implementation of the August '20 release, the Custom Reports functionality can still be accessed and used in its full capacity.
On the date of the Custom Reports deprecation with the February '21 release:
- You can still access Custom Reports, but reports will no longer run in any capacity. This means that reports cannot be downloaded, refreshed, or delivered or have any action taken on them that involves retrieving data.
- All custom reports will be migrated automatically to Reporting 2.0.
- Any equivalent security configurations will be applied to existing security roles.
- You can opt out of having your custom reports migrated automatically if your organization has already done the migration itself and/or does not need the existing custom reports.
Permissions in Reporting 2.0 are different than the permissions for Custom Reports. Custom Reports had a "Manage" permission for creating and editing reports and a "View" permission for viewing reports, whereas Reporting 2.0 permissions are more granular and users need to be given multiple permissions in order to create or view reports.
It is important to be aware of the differences between permissions in Reporting 2.0 and those in Custom Reports so that users have all necessary permissions to begin using Reporting 2.0.
To understand which permissions your users need to create and view reports, see the following information in Online Help: