The following enhancements are made to Reporting 2.0 as part of this patch release:
The Import Custom Reports tool has been updated:
- Aggregated Fields - Custom Reports with aggregated fields can now be migrated to Reporting 2.0.
- Reports with Incompatible Fields - Prior to this enhancement, report imports that failed as a result of incompatible fields required the user to delete those fields manually in Custom Reports before attempting the import again. With this enhancement, the incompatible fields are removed automatically upon import. Once imported, a message displays in the import tool indicating which fields were removed.
Note: When migrated to Reporting 2.0, a report that is not summarized will conform to the aggregation behavior in Reporting 2.0. In order to replicate the results from your report in Custom Reports, you can summarize the report in Reporting 2.0.
The following exception reports are now available:
- Competency Name
- Completion Date
- Expiration Date
- Goal Assignment
- Goal Rating Score
- Goal Rating Title
- Goal Target Date
- Goal Title
- Performance Review Due Date
- Review Period Start Date
- Section Name
- Sign-off Declined
- Step Reviewer ID
- Step Reviewer Name
- Step Status
- Step Title
- Task Final Rating
- Task Final Rating Text
- Task Name
- Task Raw Rating
- Task Raw Rating Text
- Task Status
- Task User Title
- Dev Plan Action Step
- Dev Plan Action Step Due Date
- Dev Plan Action Step Progress
- Dev Plan Activity Type
- Dev Plan Approval Date
- Dev Plan Category
- Dev Plan Date Created
- Dev Plan Description
- Dev Plan Due Date
- Dev Plan Is Primary
- Dev Plan Objective
- Dev Plan Objective Progress
- Dev Plan Progress
- Dev Plan Status
- Dev Plan Template Title at Plan Creation
- Dev Plan Title
To use exception filters for these reports, add the Exception Filters section to the Builder tab for the report. The exception filters are only available for the fields that apply to these report types. For more information about creating exception reports in Reporting 2.0, See Exception Reporting.
The permissions needed to view the exception report filters are the same permissions needed to see the non-exception version of the reports.
The Archived from Transcript? (Curriculum) field is now available in Reporting 2.0. This field is used in Curriculum Transcript Reports and indicates whether or not the child learning object (LO) of a curriculum has been moved to the user's archived transcript. The report displays "Yes" if the child LO has been archived and displays "No" if the LO is not archived.
The Past Due Aging field can now be added as a filter. This filter lets you report on users who are X number of days past due on training, which is important data for compliance purposes.
This filter is available for Learning reports.
Previously, a blank row appeared at the top of the report when the report output was constrained for the users. This occurred when running the report or exporting it. Blank rows also appeared when the Show distinct rows option was disabled in report properties, resulting in a duplicate of each row that was supposed to be hidden due respective to the user’s constraints.
With this enhancement, blank rows will no longer appear.
The time to load the report designer page is reduced. This optimization primarily impacts large portals, but all portals will now have a faster load time.
Additional certification fields are available and were initially announced as part of the February '20 release. See Reporting - Certification Fields.
The Reporting 2.0 functionality must be self-enabled. For self-enablement information. All clients can opt-in to Early Adopter in Stage, Pilot, and Production portals. See Enable Reporting 2.0.
Each Early Adopter client should have a stakeholder experienced with building custom reports. The stakeholder(s) should build report templates and share them with other users. The other users do not need Custom Reports experience, as they will simply be using templates and downloading reports. Note: Without a stakeholder with fair to moderate Custom Report experience (or comparable experience with a reporting/analytics tool), the user experience may not be as successful.
For the full list of existing permissions and their relationships, see the permissions spreadsheet in Online Help.