0.2.5 • Published 9 years ago

sense-calendar-heatmap v0.2.5

Weekly downloads
6
License
MIT
Repository
github
Last release
9 years ago

Calendar Heatmap

Qlik Sense Visualization Extension with a diverging color scale. The values are displayed as colored cells per day. Days are arranged into columns by week, then grouped by month and years.

Screenshot

npm.io

Installation

  1. Download the latest version
  2. Qlik Sense Desktop
    • To install, copy all files in the .zip file to folder "C:\Users\%USERNAME%\Documents\Qlik\Sense\Extensions\swr-CalendarHeatmap"
  3. Qlik Sense Server

There is also a demo available, if you want to see a working example.

Configuration

After installing the extension the following properties can be set:

Data Definition

PropertyDescriptionValues
Unique dayField containing the unique day. Note that you just have to type in the field name without equal sign (=).Example: Dim1 or [Dimension with Space]
ValueExpression which needs to result in a valid numeric number (positive or negative).Note: Define the expression without a leading equal sign (=).Example: [round(Sum([TableX.FieldWhatever]),0.001)
Tooltip:You can (optionally) define the tool tip display when hovering a day.

Appearance / Debug Mode

If you want to see which data are passed to the Calendar Heatmap visualization, you can temporarily enable the Debug Mode. By doing so only the data returned from the QIX engine will be displayed in a table.

The Debug Mode can only be activated and you'll only see the resulting table in Edit Mode of Qlik Sense.

Limitations

  • For performance reasons only 1500 rows will be returned (so 1500 days).

Ideas for Improvement

I'd like to look into the following areas to improve this Visualization Extension for Qlik Sense:

  • Skip rendering of years not included in the data
  • Performance improvements
  • Better, configurable label
  • Offer also a week view and maybe other views
  • Support selections (both single days, weeks and years)

Contributing

Contributing to this project is welcome. The process to do so is outlined below:

  1. Create a fork of the project
  2. Work on whatever bug or feature you wish
  3. Create a pull request (PR)

I cannot guarantee that I will merge all PRs but I will evaluate them all.

Author

Stefan Walther

Change Log

See CHANGELOG.md

License & Copyright

The software is made available "AS IS" without any warranty of any kind under the MIT License (MIT).

See Additional license information for this solution.