Historical Discover date ranges not available in ad hoc analysis

In the ad-hoc analysis capability, a discrepancy is possible between the date ranges available when creating a project and after a project is created. These differences are due to ad-hoc analysis processing platform changes.


This article does not affect report suites created after November 1 2010.

Solution 1: Compare available date ranges

Creating a project: ALL dates that had ad-hoc analysis enabled are available, including dates processed on Legacy Date Slices.

Editing an existing project: If selecting a date range after slice processing was discontinued, you can only select data back to when this new processing began. It can be as early as November 2010, but most likely later depending on report suite.

If selecting a date range that used legacy slices, only the current slice's date range is available. A three-month slice is used if the date range selected could fit in that slice. Or, a yearly slice is used if it is larger.


You cannot see data originated from both legacy slices and the new processing platform. If you attempt to pull a date range that spans both, the following error message appears:

The date range you requested spans a data boundary, and cannot be fulfilled. Your range has been changed.

Solution 2: Switch projects between processing platforms

If you have worked on a project that requires changing the date range to a different platform, do one of the following:

  • Change Project: Go to File > Change Project. This option allows you to change the report suite and date range while keeping the existing tables you have created.
  • Save the current project, and reopen it: Go to File > Save Project, and give your project a name. once it is saved, click File > Open Project, and select a different default date range before opening the project.
  • Create a project: Go to File > Create New Project. This option allows you to start fresh with the new date range.

Additional resources

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy