Page Comparison

Celoxis enforces certain limits on data retrieval for reports. This is because running certain reports results in colossal amount of data which not only slows down your application, but also impacts others. Such data is not even relevant for decision making or relevant.

Described on the page below are the various limits set on report data and the error messages you will see when your data exceeds those. It also explains the action you can take. As your data grows fetching all that data slows down the loading of your pages. In order to keep the application responsive we have enforced some limits. The table below lists the the limits, the error/warning messages and the actions you can take to reduce the data.

Error Message	Reason and

ChangesAction requiredReport resulted in too many recordsIf a report returns more than 15,000 rows of data, you will see this message. After a couple of weeks, you will not see the data and an error will be displayed on the report.

Edit report to add more filters to your reports.

For Example:

In a 'Project' report, add

Actions required to fix it

Report exceeded limit of 15,000 records.

A limit of 15,000 rows for any report is enforced.

To fix this edit the report and add filters or use the promptable filters defined. For Example,

In 'Project' reports, use filters such as "Manager", "Client", "Phase" or "Category"

, etc to see relevant data

.

For a "

In 'Time entry

" report

' reports,

add

use filters such as "Date", "State", "Time code"

, etc.Pagination limit exceeded

There is a maximum records per page limit on reports.

When the report is loaded on your dashboard, this limit is 50 records per page.
For an individual report, it is set to 250 per page.

No action is necessary from your side. When we enforce these limits, your per page record count will automatically readjust to those limits.This report is no longer supported on the dashboardThis message will appear on all Gantt Reports and Resource Load Charts that are on your dashboard. These reports consume lot of server & client resources and are one of the primary reasons for slow-loading dashboards. Dashboards are the top-visited links in the application and hence having these resource-intensive reports can cause severe performance degradation. Please remove them from your dashboard and access them individually. They will be automatically removed from your dashboard in a couple of weeks, if not manually removed.Resource load chart

.

In most cases you are interested in recent data. So the easiest way to limit data in any report is to use date filters.

For any Time-Phased report: Date range exceeds limit of

3 / 12

'n' months

For

The Period filter on the Resource Load Chart

, we will also enforce some zoom limits as follows:

When "Zoom" is Day, your data will be limited to a Quarter.
When "Zoom "is Week or Month, your data will be limited to a Year.

Please fix your Zoom & Period filters as mentioned. These will be automatically enforced in a couple of weeks, if not manually fixed.Weekly Time: Filter Tasks for "In range" cannot exceed 3 monthsThe In Range option under "Filter Tasks" on the Weekly time screen is now limited to 3 months. Ensure that the In Range option under "Filter Tasks" on the Weekly time screen should have a date range which does not exceed 3 months. These will be automatically enforced in a couple of weeks if not manually fixed.

...

is limited based on the Zoom level. The value of 'n is'

3 months for Day zoom
12 months for Week or Month zoom.

You can change this or it will be enforced automatically.

Timesheet: Work Items exceed 1000

The Work items on the Timesheet are limited to show 1000 records (tasks and app items on which you can fill time).

Info
The Resource Load, Gantt reports, Incomplete Timesheets reports are not available for the dashboard as they cause performance degradation.

Versions Compared

Old Version 2

New Version Current

Key