Calendar attribute troubleshooting

The calendar feature is an advanced feature in Decision Insight. You need to purchase a license with the calendar option to use this feature.

Runtime attribute always has the default period values

1. Check the license

If you are in one of these situations:

  • your active license does not have the calendar option.
  • your license with the calendar option has expired.
  • your trial period ended.

The Calendar feature runs in disabled mode and always evaluates the value of the Default period for all runtime attributes.
In this case, Decision Insight displays a warning banner on top of the Calendars screen and produces warnings in the log.

To fix this issue, purchase a valid license with the calendar option and install it on each node in your deployment.

See also Activating the calendar feature.

2. Check the configuration

Make sure your Calendar Configuration contains an active rule at your reference time. If no rule is matching, then the default period is selected.

To confirm the current period is evaluated the way you expect, you can follow these steps:

  • Create a new calendar attribute as a manual constant of type String; assign the related period name as value.
  • Create a dashboard to display the runtime attribute you just created.
  • Navigate the time machine to check the current period at any time.

3. Check the configuration attribute

Make sure you entered the correct values for your calendar-based attribute configuration.

If the attribute is a manual constant or manual thresholds:

  1. Open the constant editor: 
    • From the Calendars screen, click the Create calendar attributes hyperlink.
    • Or from the multi dimensional entity created for period type entity of your calendar and its linked entity(s).
  2. Modify the values as needed. (warning) Mind the different versions of your attribute.

If the attribute is observed:

  1. Create a datagrid pagelet in a dashboard.
  2. Set the period type entity of your calendar and its linked entity(s) as dimensions.
  3. Select your attribute (the one without the calendar icon) as value.
  4. Navigate your dashboard to check actual values meet your expectations. (warning) Navigate the time machine to check the values at any time.

Runtime attribute always has non set values

1. Check the configuration

Make sure you entered a Calendar Configuration for each instance of the entity(s) linked to your calendar.

If no valid configuration is set, all the runtime attributes of your calendar will display not set values

2. Check the configuration attribute

Make sure no values are missing for any instance of your calendar-based attribute configuration.

You can search missing values the same way as explained in the above paragraph 3.Check the configuration attribute.

Runtime attribute is not created

Calendar feature only supports attributes of type baseline (new), boolean, decimal , dispersion multipliers, duration, forecast, instant, integer, interval, string, thresholds (new).

Related Links