Reporting 2.0 - Reporting Fields List UI Improvement

Previously, it was possible to include fields in Reporting 2.0 for which the underlying data tables had not yet been created. This occurred when a new functionality was enabled, but no data was created in the portal for this new functionality. When these fields were included in a report, the report would yield an error message.

With this release, if a field is available in Reporting 2.0 but no underlying data tables have been created for the data, the fields appear gray and disabled, identifying that the functionality that corresponds with the field is available in the portal, but no underlying data table has been created. Once the newly enabled functionality is used and underlying data tables are created, the fields automatically become selectable in Reporting 2.0.

Note: Examples of sections this feature applies to are Check-Ins, Capabilities, and Capability Models. The fields are only greyed out in Reporting 2.0 if these functionalities were never used or tested in your portal. Even if the functionality is not currently in use, but has been activated in the past, the fields will not be greyed out.​

Be aware that this does not apply to Custom Fields, because underlying tables are created although data may not be populated in the portal (e.g., Transcript custom fields).

When a field is disabled, administrators can hover over the field to view an explanation of why the field is disabled.

How Does this Enhancement Benefit My Organization?

This feature provides interface improvements in the Reporting 2.0 fields list to denote field data unavailability in the portal.


Upon implementation, this enhancement is available for all portals with Reporting 2.0.

Click here to download the Reporting 2.0 Adoption Kit.


For more information about Reporting 2.0 permissions, see the following:

  • Permissions in Reporting 2.0 - This provides detailed information about Reporting 2.0 permissions.
  • Permissions List - This provides the list of permissions and their relationships so that you know which permissions users need to have to create and view reports.