Error Received: [The time periods requested do not exist. Review the column's Time Scale settings.] after changing timescaled view configurations.

Document ID : KB000028482
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Error received: [The time periods requested do not exist. Review the column's Time Scale settings.] after changing timescaled view configurations within views/portlets such as the Resource Utilization page under the Task Tab or the Team Utilization portlet used in the Dashboard.

Solution:

There are limits to what can be display within the TimeScaled field within views/portlets such as the Resource Utilization page under the Task Tab or the Team Utilization portlet used in the Dashboard.

These are internal timeslices that can not be configured.
Internal timeslice range is as follows:

28 Daily - One week in the past, the current day and 3 weeks in the future
16 Weekly - 2 weeks in the past, the current week and 13 weeks in the future
36 Monthly - 4 quarters in the past, the current quarter and 7 quarters in the future
Year, Quarter and Monthly periods all use monthly slices
Weekly period uses weekly slices . Daily period uses daily slices

Resolution:

Follow these guidelines when setting up Timescaled view period information.

The numbers of periods available are limited in the following manner:

Year: may set 3 periods - viewable data will be available for the following range:
1 year in the past to 2 years in the future.

NOTE: 1 year in the past is only available if the current date is in the first quarter of the year. Once the slices roll over, only 3 quarters in the previous year will be available; as this is less than a full year, you will get the error if you are requesting dates from a year in the past.

Quarter: may set 12 periods - viewable data will be available for the following range:
4 quarters in the past and 8 quarters from current period to future.

Monthly: may set 36 periods - viewable data will be available for the following range:
12 months in the past to 24 months from current period to future.

Weekly: may set 16 periods - viewable data will be available for the following range:
2 weeks in the past to 14 weeks from current period to future.

Daily: may set 28 periods - viewable data will be available for the following range:
7 days in the past to 21 days from current period to future.

The start date that you choose - be it rolling or specific must fall within the date ranges listed above. The date which determines the past/future line is the current system date.

These data ranges may not be changed by end users, nor through customization to the system. Even if you have timeslice data that is outside those ranges, the system still limits the view to the ranges specified above.

Therefore, even though you may have weekly and daily data within your requested range for example as far back as January 1 2005 to October 25, 2005, because that date range does not fall within with the limits for Weekly and Daily you will see the error telling you to check your timescale configuration.

More Information:

The time-scale views setting are dependent upon the system Time Slices which are not configurable by the end user.

The Monthly, Quarterly, Yearly slices rollover quarterly. So 22 months, 7 quarters and 1 year will only be available during some months.

Our teams are collecting feedbacks and use cases through this enhancement idea of adopting a different architecture that will avoid the situation described above. Here is a link to an idea for this issue: Allow Administrative control over time slice ranges on OOTB System Data Providers

We encourage you to review and vote up!