Quick #Qlikview Reloader

We all know and love the QMSEDX reloader and it works well. The way I was using it though was getting a little annoying. Typically I would set the password on the External Event Trigger. Then I would create a .bat file that would call qmsedx.exe something like

\\server\QMSEDX_CommandLine\qmsedx -task=”Reload a Qlikview” -qms=http://server:4799/QMS/Service -password=thepassword

Then go into the qvw, create a text object and set then the action to launch the .bat file

Kind of a hassle.

So my first thoughts were I could just delegate access to the Qlikview portal and let people reload that way. But I was a little hesitant because there was no way to restrict them to reloading only. They could muck up the schedule, delete tasks, all sorts of ways to mess things up.

Anyways, I wanted a method that was easy to reload but had a low chance of people messing with it.

Enter the Qlikview reloader.

First off, I stopped using a password on the EDX task. (A user can’t reload unless they are a member of QlikView EDX anyways)

Basically it looks in the C:\ProgramData\QlikTech\ManagementService\QVPR\Trigger.xml for where the TriggerType for ‘ExternalEventTrigger’ is ‘true’. This gives you a list where EDX has been set, then it joins to the C:\ProgramData\QlikTech\ManagementService\QVPR\DocumentTask.xml to get the name of the document

Then a text object is created with a conditional show that will show when a single document is selected.

=if(GetSelectedCount(DocumentName)= 1,1,False())

This text object has a Launch action the application is set to


This assumes you have downloaded the qmsedx.exe and created a share called QMSEDX_CommandLine

Also, need to set the vServer parameter

The Parameters are

=’-task=”‘ & only(DocumentName) &'” -qms=http://$(vServer):4799/QMS/Service -verbosity=5’

This launches the reload and passes it the document name, I also find it useful to include the verbosity=5 so that you can see some progress in the reload window.

In action it looks something like this.

Qlikview Reloader

Get a copy here





How to transfer state using the IE Qlikview Plugin, solved

I’ve been slacking a bit on my blogging 🙂

After some trial and error I was able to transfer state from one Qlikview to another using the IE plugin on the Qlikview server.

The first thing to figure out is the path to your Target Qlikview.

The easiest way to do this is to open up the qlikview on the portal and then press Control + Shift + Q (Or go to the menu of the Qlikview plugin and choose Document Support Info)

transfer state

Copy that address. I’m not sure why it uses the qvp protocol, but hey this works.

Ok, now on your starting Qlikview you need to have a field that matches exactly a field in your target Qlikview. Otherwise it won’t work

So create a button, choose ‘Open QlikView Document’ paste in the URL you got from before (You can remove the qvp://qlikviewservername/ if you want)open

Click Transfer State.

Now publish your starting Qlikview (the button won’t work from Qlikview desktop)

And press the button. If everything works correctly you should see selections passed from one Qlikview to the Next. (If no selections are possible on the target, nothing will happen)

Qlikview resetting variables during reload, solution

From http://community.qlik.com/thread/39123

Re: Preventing variable reset on reload
Ryan O'SullivanApprentice


I have come across a possible workaround that is working in my environment.

In the document properties/variables tab, for each of the user variables i have ticked the box for “Include in Bookmarks”. After several document reloads using publisher the variable values are being retained after each refresh. I was having a similar issue with Date variables changing back to defaults and now it appears fixed.

Note: You need to reload it a first time, then change your variables and reload again to see the changes is working.



#Qlikview QlikTech Open Data Challenge, Do you Realize

So Qlikview recently ran a ‘Take Action Open Data Challenge’, basically use Qlikview on public data to uncover unexpected insights to positively change the world.

The 1st Place winner was ‘Do you Realize’ created by Alexandre Perrot, and Software Advice wrote a post on how he goes about developing dashboards.

The first point is to Think about the data. This is a great reminder, thinking through a problem can often times save you a lot of time later.

The author recommends a snow flake schema, this is pretty typical Qlikview recommendation.

He then next thinks about what the user is going to click and interact with. He started out with an overview screen.

This qlikview is very much an example of information storytelling, something Donald Farmer would no doubt approve of.

do you realize

Clicking on Start tests your knowledge of what potentially will occur as far as population growth and environmental changes. It scores you as you move through it. Clicking on the leaf or the heart on the side takes you to the Environment or Health pages. Clicking on the word ‘environment’ or ‘health’ takes you no where, I would assume those button-like objects would take you there as well. Slightly annoying.

As you move through the quiz you are given the opportunity to learn more, which will take you to the salient detail screen… continuing your knowledge foraging. I did wish that I could click back to where I was in the quiz instead of having to restart each time though.

After the Overview screen he advises to create screens that help a user understand a given KPI.

He advises using color to convey change. I agree completely… but in this case I think too much color and too much chart junk is used. http://www.perceptualedge.com/articles/visual_business_intelligence/rules_for_using_color.pdf


I find the use of color a little overwhelming. I would remove the ‘blue haze’ behind the map. I do like the map it is very visually appealing. I’m not a big fan of the pie chart, neither do I like bubbly iphone’ish pie charts.

Overall I agree with the points laid out by the post. I would recommend a simpler approach, but that just my 2 cents.

#Qlikview Responsibility Box

So this is a simple idea so that users know who to go to with questions about specific Qlikview i.e. who is the ‘SHMEEEE ‘

So use a variable in the load script

vDocOwner = ‘youremailaddress@somewhere.com’

Now create a text object displaying the vDocOwner

If you want to be extra fancy (For extra fancy you can even include the name of the document in the subject…. & subject=)

In its properties, on “Action” tab, choose : “Open URL”

In the command line, write :


Now if they click on they can send the responsible party an email….

There, enjoy extra responsibility responsibly




Also, I should make a link to a wiki page that describes the Qlikview but I will save that for later.

#Qlikview rules of thumb

This is a short list but will continue to add more. These are mainly coming from the Qlikview masters summit

Declare all variables in the script (Especially important if you use source control)

Drop the seconds from DateTimeStamps if not needed (probably not needed most of the time)  I’ve been using cast(TheDate as Smalldatetime) as TheDate as a SQL way of doing it (any better ways??)

IF’s are evil, especially if the execute for every row

How I’ve been #Qlikview ing lately, update

So in addition to the below


And I also started using subversion for source control


I also like to make a simple little deploy .bat file. This guy copies over my changes, and then runs an EDX command (setup your reload with an EDX task) This way I can check my changes on the server.


xcopy “C:\Working_Qlikview\Financial Statement New.qvw” “\\qlikview\c$\Qlikview\QlikView Storage\Private Data\Source Documents\In Production\Accounting\Stuff.qvw”

ECHO Please Wait While Data Refreshes
\\qlikview\QMSEDX_CommandLine\qmsedx -task=”Distribute Stuff” -qms=http://qlikview:4799/QMS/Service -password=apassword