Qlik Sense / Qlik Analytics Platform Articles, Projects & Tutorials by Stefan Walther

The Custom Component API

How does the API behind the concept of custom component look alike?

The Custom Component API follows the same principles as when developing a Visualization Extension.

If you have never created Visualization Extension, it is highly recommended that you first have a look at the following document:

Ingredients of a Custom Component

A Custom Components contains the following elements:

  • A definition file (.qext file)
  • A main JavaScript file
  • Other (optional) assets, such as JavaScript libraries, images, fonts, etc.

The Definition File

  • The definition file is the main entry point for Qlik Sense to load a custom component.
  • A definition file always uses the file-extension .qext


  "name": "ccs-boilerplate",
  "description": "Boilerplate for a custom component.",
  "type": "component",
  "version": "0.1.0",
  "author": "Stefan Walther"

The following properties are mandatory for a valid definition file:

  • name - The name of the custom component.
  • description - Any meaningful description for your component. Not used anywhere in the product right now, but important for future versions of Qlik Sense.
  • type - Type of the extension, should be always component for Custom Components.
  • version - Version of your custom component, uses the concept of Semantic Versioning .
  • author - Some information about the author.

Further properties can be added to the .qext file and it is highly encouraged to do so. Additional properties provide very helpful information
Follow the standards of npm's package.json definition.

The Main JavaScript File

Custom Components are (right now) basically AngularJS directives.
The purpose of the JavaScript file is to return the signature of an AngularJS directive.


define( [], function () {
    'use strict';
    return {
        name: "ccsBoilerplate",
        restrict: 'E',
        link: function ( scope, element, attrs ) {
            element.html( 'OK, we have a custom component.' );
            console.log( 'OK, we have a custom component.' );
} );


Technically speaking it would work also to register your directive with qvangular.directive( ... but you should never do so, because the concept of Custom Components could be extended in the future far beyond just AngularJS directives.

Naming of the Component's Name (camelCase)

The property name should match what you have defined in your .qext file.
But if you compare the name property of the .qext file with the name property of the JavaScript file, you'll see a difference:

  • name property of the .qext file: ccs-boilerplate
  • name property of the JavaScript file: ccsBoilerplate

We have already seen in the previous chapter that one would use the Custom Component with the <ccs-boilerplate></ccs-boilerplate> Html elment.
The reason for the difference between the AngularJS directive signature and the definition file is that AngularJS follows the principle of camelCase .

Angular normalizes an element's tag and attribute name to determine which elements match which directives. We typically refer to directives by their case-sensitive camelCase normalized name (e.g. ngModel). However, since HTML is case-insensitive, we refer to directives in the DOM by lower-case forms, typically using dash-delimited attributes on DOM elements (e.g. ng-model).

(taken from the AngularJS documentation: "Directives")

Prefixes for your Custom Component

The given example of ccs-boilerplate uses the prefix ccs (which stands for custom components sample).
Use prefixes of your Custom Components to prevent conflict with components created by other developers.

You should not used the prefix qw, which is reserved for Custom Components provided by Qlik, such as qw-sys-info.