The code corresponding to the time granularity.

Examples of common levels are year, quarter, month, week, and day.

Values: any value except Y, which is reserved for the year level, and D, which is reserved for the day level.

Required

The ordinal value of the level.

Values: the top level of the hierarchy must be assigned a level_number of 1; descending levels in the hierarchy must be numbered sequentially

Optional

The external object identifier for a period name. The language_text_id is used as the default period name if no period is provided in the time language text file.

Optional

The time level that is used as the parent in a history chart.

Optional

The rule used to assign a time period to a parent time period when the time period start and end dates don't fall within the parent time period start and end dates. If null, the dates must be contained within the parent’s dates. Metric Studio will allow only one time level row to contain a non-null value for parent_link_rule.

As parent_link_rule is typically used to define calendars containing weeks, the week example is used in the descriptions of the values.

Values: FIRST_DAY_IN_PARENT (the week will be contained in the month where the week begins), LAST_DAY_IN_PARENT (the week will be contained in the month where the week ends), MOST_DAYS_IN_PARENT (the week will be contained in the month where most of the week’s days fall)

Optional

The date the object was created.

Format: yyyy-mm-dd hh:mm:ss (24-hour clock)

(hh:mm:ss values are optional)

Required