stefanwalther/qliksense-extension-tutorial

A comprehensive tutorial how to create Qlik Sense Visualization Extensions.

Qlik Sense Extension Tutorial

A comprehensive tutorial how to create Qlik Sense Visualization Extensions.

---

About this Tutorial

In this tutorial you'll learn how to use Qlik Sense' Extension concept to bring new visualizations into the Qlik Sense Client.

Work in Progress, Always

This project is work in progress and will and should always remain in this status, that's part of the concept and the idea of creating a living tutorial. As soon as there are now capabilities exposed in Qlik Sense' Extension API, I will update the appropriate sections here.

If you want to follow the progress of this project there are some options:

• Join GitHub and "watch" or "star" the project and you'll get updates
• Follow me on Twitter, as soon as I have finished a new chapter, I'll announce it there

Chapters

These are the chapters I am about to write ... and some of them are already finished ;-)

• Part I: Introduction to Developing Visualization Extensions for Qlik Sense
• Part II: Qlik Sense Visualization Extensions & AngularJS
• Part III: Advanced Concepts When Working With Qlik Sense Visualization Extensions
• Part IV: Deployment of Qlik Sense Visualization Extensions
• Part V: Advanced Techniques
• Part VI: Real World Examples
• Part VII: How To
• Part VIII: Tools
• Part IX: Appendix

Comments, Feedback & Questions

If you have any questions, found errors, etc., please create an issue here on GitHub.

Contributing

Found a bug? Have a request? Have a question? Please create an issue on GitHub.

Errata

Due to the nature of this project there is no errata section necessary: This is living tutorial, so as soon as I find errors or mistakes or just want to improve something, I'll just fix it and push it to GitHub.

By doing so, you'll always have access to the latest version.

If you want to follow changes, follow the Change Log.

Author

Stefan Walther

• github.com/stefanwalther
• twitter.com/waltherstefan
• qliksite.io

Thx for contributing:

• mcgovey

License

Copyright & License

Copyright © 2016, Stefan Walther.
Licensed under the Creative Commons Attribution 4.0 International (CC-BY-4.0) Open Source license.

qliksense-extension-tutorial's Issues

Cannot read property 'qInterColumnSortOrder' og undefined

Hi Stefan - Thanks for an awesome tutorial, enjoy the angular part.

When I try to follow the example in the tutorial - the following error appears: qInterColumnSortOrder?

Changes are not reflecting in Qliksense extension

Hi,

I followed every step mentioned.
But still every time I have to close the Qliksense desktop and start it again to see the changes.
How can I solve this issue? Is there any setting I missed ?
Please help me out on this.

Thanks, Nitin

Not able to insert dimensions and expression in Qliksense Heatmap

Hi

We have developed our own qlik sense heatmap chart.
I am new to javascript.Could you please share how to insert our own dimensions and expressions in below code.

Thanks

Typo on part-01/ 05-Improving-the-Hello-World-Experience Page

There seems to be a small error in the part-01/05-Improving-the-Hello-World-Experience:

Should be myDynamicOutput

Request: Using show-service-popup-dialog with custom properties

If it's possible and fairly easy to use the popup service Qlik Sense uses for adding dimensions/measures/data for your own custom properties I would like to read a tutorial on that topic.
This would be useful when you create a hypercube on the fly, now that arrays/list are supported.

Table API

Describe the new Table API in 2.1

Broken link

Hi thanks for the tutorial.

There is a broken link on this page: http://qliksite.io/tutorials/qliksense-visualization-extensions/part-01/02-Introduction-to-QlikSense-Visualization-Extensions/#
Regarding how to deploy visualizations in Qlik Sense Server.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Missing closing brackets

https://github.com/stefanwalther/qliksense-extension-tutorial/blob/master/tutorial/part-01/09-Loading-Resources.md#2-adding-a-link-to-a-style-sheet-to-the-documents-header

define( [
"jquery"
], function ( $ ) {

    $('<link rel="stylesheet" type="text/css" href="/extensions/my-extension/css/myStyle.css").appendTo("head");

} );

missing closing brackets >'
Should be:
define( [
"jquery"
], function ( $ ) {

    $('<link rel="stylesheet" type="text/css" href="/extensions/my-extension/css/myStyle.css">').appendTo("head");

} );

Custom Sections issue with properties

I have noticed that when I create a custom section and header that my custom properties don't get "initiated" until the user edits each of the properties. This causes problems since the property isn't available until the user edits everything. Prior to having a custom section (using settings), all of the properties populated automatically.

Is there a setting/command needed to be executed to instantiate the custom parameters?