topic Re: Is there a dummies guide to developing Document Extensions? in QlikView

Is there a dummies guide to developing Document Extensions?

Mon, 26 Jan 2026 16:26:21 GMT

Or just some best practices to follow when creating your own ones?

Currently I'm doing the following:

Create folder for Extension, containing
- Definition.xml
- Script.js
- style.css
Copy the folder to C:\Users\[USERNAME]\AppData\Local\QlikTech\QlikView\Extensions\Document
- It now should appear as a document extension
Open up my .qvw document in QlikView desktop
Add my new extension to the document then save
Deploy my Document onto QlikView Server
Deploy my Extension to QlikView Server
Browse to the Access Point in my browser (Chrome), then open the document
On the server itself, explore to where I deployed the Extension and open up the Script.js and style.css files

...and now I'm ready to start working on my Document Extension, make changes to the files, refresh, debug and inspect in my browser.

Is there an easier way of doing this?

Re: Is there a dummies guide to developing Document Extensions?

oscar_ortiz — Thu, 01 Aug 2013 17:15:21 GMT

I would check out Stephen Redmond's blog www.QlikTips.com or check out the direct link to his beginners guide: http://www.qliktips.com/2011/01/beginners-guide-to-qlikview-extension.html

Re: Is there a dummies guide to developing Document Extensions?

Fri, 02 Aug 2013 08:05:39 GMT

Thanks Oscar, but that blog only covers Extension Objects, not Document Extensions

Re: Is there a dummies guide to developing Document Extensions?

patrik_seger — Mon, 12 Aug 2013 10:43:33 GMT

I guess that this is the way (neatly described).

If you just want to inspect what you are doing, you could add a

Qva.LoadScript('https://getfirebug.com/firebug-lite.js#startOpened', function() {

...

});

in your script and then look at HTML/CSS/Script directly in QlikView Desktop (skipping the Server steps). No support for breakpoints though...

But due to lack of breakpoints and stepping, I also run all my development from a server.

Br Patrik

PS!

To automate the process, I use grunt.js (http://gruntjs.com/) to simplify development of extensions. Change the code, run grunt and then test. Some work to set up the environment though but if you are into heavy extension development then its well invested time.

DS!