Limitations and considerations in Reports

The Reports app works differently from other Diligent One apps. As a result, there are a variety of limitations and considerations to be aware of when using the app.

Number of projects

If you are running into errors when creating reports, you may be trying to process data from more projects than Reports can process. See Configuring filters in reports to filter down the number of projects included in your report before running it.

Number of time entries

The Timesheets view can show a maximum of 20,000 time entries. If your report includes more time entries than the limit allows, we suggest reducing the number by creating a filter with the Time Entry Date field.

Number of custom attributes

Reports supports reporting for a maximum of five custom attributes per risk, control, or other component for which custom attributes may be added (such as actions, results, and others). Projects allows up to 10 custom attributes per component, meaning that any custom attributes beyond five will not appear on custom dashboards generated in Reports.

Activity Center, currently in beta, supports full reporting capabilities for up to 10 custom attributes. For access to Activity Center, contact your customer success manager.

Time zone settings

The Reports server time is UTC. Almost all system times in Reports display as UTC. However, you can specify a time zone when setting up a report broadcast schedule.

Language settings

To use Reports in a specific, supported language, you must set the language in your browser settings. Reports does not respect your Launchpad profile for language settings.

Using "by Entity" Views

Views define the categories and fields from Diligent One that you can use to build a report. Fields are specific columns of data and categories are logical groupings of fields within a View.

The "by Entity" Views are intended for report writers that want to specifically include the Parent Entity, Entity Category, or Entity field in their reports. Entity fields in these Views are used to split data.

For more information, see View reference.

Disabling Auto Refresh when building a report

Auto Refresh is a setting you can configure when you build a report.

Disabling Auto Refresh builds your report with dummy data, and enables faster performance. If you need to retrieve actual data after adding fields to your report, you can manually refresh the report by clicking Refresh Report in the lower-right corner of Report Builder.

For more information, see Creating reports.

Retrieving data from projects and collections

If you need to retrieve data from a single project or a specific set of projects, you can filter your report by the following fields:

• Project Name
• Project Folder
• Project Type
• Report Opinion

If you need to retrieve data from a single collection or a specific set of collections, you can filter your report by Collection Name.

For more information, see Configuring filters in reports.

Generating reports faster

To avoid errors caused by processing too much data at once, and to reduce the likelihood that the report will fail to generate due to containing too much data, see Using filters to generate reports faster for a list of fields you can use to filter the data going into your report. The available fields vary depending on the View you're using.

For more information, see Configuring filters in reports.

Working with multiple reports

The Reports app only supports a single session. Opening Reports in another browser tab in order to work on multiple reports or compare reports side-by-side is not supported.

For optimal performance, use Reports in a single browser tab.

Database caching

Reports uses a 20-minute database caching process in all regions.

Once you create and save a draft or an active report, report data is cached in the database. Subsequent modifications to the report loads data from the cache.

To invalidate cached data in reports, you need to do one of the following:

• Go to Launchpad and return to Reports
• Sign out of Launchpad, sign in to Launchpad, and access Reports

Removing users or user access to Reports

The Reports app does not handle the removal of users automatically. Removing a user's access to Reports can also result in unintended consequences:

• Any private content that the user created becomes inaccessible for everyone else.
  Note

  This can prevent other users from removing folders in Reports, as all content must be removed from a folder before you can delete the folder. To remove these folders, contact Support.

• Users can still be assigned report broadcasts.
• Users can still receive report broadcasts. The data that they see in the report depends on:
  • their access permissions in other Diligent One apps (see Access to HighBond data )
  • if they have been removed from Launchpad or have no access in other Diligent One apps (the report contains no data)

To completely remove a user from the Reports app, contact Support.

Troubleshooting system errors

If you receive a generic error message that prevents you from accessing the Reports app, a system error may have occurred. Wait five minutes, and try logging in to Diligent One again.

If you still see the error, try one of the following options: 

• Clear cookies in your browser.
• Use another browser to access the Reports app.
• Access Reports using a private browsing window (Internet Explorer, Edge, Firefox, Safari) or Incognito Mode (Chrome).

If, after trying all of the above options, you still cannot access Reports, contact Support.