There is no perfect relationship. Your girlfriend is a little bit possessive, your roommate could use a shower once in a while and your boss always freaks out when you’re late. Come on, even QlikView has some flaws that you’d be happy to change.
Here’s my list of the most annoying things I’ve found as a QlikView consultant. If you’ve been creating apps for a while I’m sure that you’ll relate to some of them…
First things first: we will start our list with the splash screen. For those of you who are not familiarized with this term, the splash screen is that green window that pops up every time you open QlikView and disappears almost immediately. (I know… “immediately” is a vague term.)
If you’re developing small applications in your PC this will hardly be an issue. However, if your computer lacks capacity, you work with multiple QVWs at the same time or have an important presentation with key customers, it tends to… linger a little more than usual.
Typically you can click on it and start working right away, but when this little friend it’s not in the mood, it stays there blocking your visibility even if you change the active window. Sometimes it stays green, other times it turns black, but if you’re on a hurry it will surely be annoying.
Maybe patience is not my strong suit, but there are several posts around the web that show how to get rid of it… I can’t be the only one…
Ordering a QVD
Premise 1: The simplest commands are always the most powerful. The functionality provided by clauses like WHERE, GROUP BY and ORDER BY is vital for developers.
Premise 2: QVDs are great, they are incredibly small and fast files that can contain a lot of information.
The problem: Sadly, it is impossible to use ORDER BY when loading a QVD file. Yes, I know I can read the table and then sort it in a resident load… It’s just not cool…
Is it reloading?
The Script Execution Window is a great ally when you’re working with “temperamental” databases, tables with millions of records or applications that use multiple data sources. As you know, it contains useful information like the time elapsed, the database connections and the number of records loaded so far.
However, every now and then, when you reload the window freezes… It turns white… And your heart stops for a minute…
You can always open the Task Manager to see if QV is still processing… but when you’re working with heavy applications it’s never pleasant to encounter this issue.
I haven’t found this issue recently, I think they got rid of it in a Service Release or something, but it happened a lot in version 9 and 10. When you had –for example– a spreadsheet with the budgets for the next year, but each column represented a month, the most common way to deal with it was to use the CrossTable wizard.
However, sometimes the execution had some unexpected results… I’m sure many of you recall opening your Table Viewer to find a normal data model (no synthetic keys, no circular references) surrounded by dozens of little orphan tables like this:
Yep, you almost started crying… The classic workaround in this situation was to add an extra line to the code like WHERE 1=1.
QlikView Server logs
Monday, 8 AM.
James is in charge of the QlikView environment in his company. As usual, he starts the day with a routine QV Server check-up: reload results, RAM usage, number of users, inactive licenses, etc.
Though it looked like an average day, something was amiss. A failed reload message stained the perfection of the console. Hesitant, he opens the Task History tab only to confirm his fears. The XYZ task failed.
What to do? Whom to call? He needed a starting point for his research. Rumors say that the Log tab has some information, so he decides to give it a shot. After a few seconds of reading, James is confident that this log will solve his problems. Surely the following lines will not only contain the reasons of the failure, but also some troubleshooting ideas. Suddenly, he finds it:
James is relieved. The information given by the log was clear and useful. It surely helped him to solve the problem.
James hates QVS logs. James is not alone… I hate them too…
Working as designed
OK, maybe this one hasn’t happened to a lot of you, but here it goes.
I remember a couple of months near the end of 2012 when I found 4 or 5 bugs in QlikView. At that time I was working with a Master Reseller and the normal procedure was to create a ticket so the support team could start checking the issue.
After a couple of emails exchanging details about the hardware, software and other stuff, the support team sent you a response. If you were lucky, they would tell you that a Service Release correcting the issue was on its way. If you were not so lucky, they would assure that the technical guys were working on it and that hopefully they may come up with a response soon.
But if you were me, the answer usually went like this:
Hello dear partner,
We were able to replicate the situation you described. As you mentioned, that awesome feature you were trying to implement is not working. However, the support team does not consider this as a bug. As you can read in the QV Manual and the Release Notes for version XX, that behavior is expected:
* This functionality will not work in the AJAX client. It will probably be unstable in IE 6 or superior. Also, we wouldn’t recommend its usage if your name starts with a vowel or if it’s Thursday.
Ever had problems with the resolution of your customers’ monitors?
It’s all about the client
My colleagues often say that I have principles of OCD… Maybe, but I really freak out when I see that the AJAX client slightly changes the alignment and size of certain objects.
This is a problem that most developers have. Damn you QlikView, you’re so freaking flexible.
– Lauren: OK Mark, it looks like our app is ready for release. Please give it a final review, just in case.
– Mark: Sure, I’ll do that.
Later that day. Mark working on his own:
Mmmm… this app looks great, everything is working just fine… maybe I’ll just change this color. I don’t fully like it in blue…
– 15 minutes later: It looks awesome in green. Actually, I’ll change the whole color palette.
– 30 minutes later: You know what? This tab could use a pie chart instead of that table.
– 2 hours later: Wait, wait, great idea: scatter diagram and combo chart in a container!
– 4 hours later: Now that I think about it, we could manage QVDs differently to improve the overall efficiency of the environment.
– 7 hours (and a whole new application) later: Hi Lauren, our app is ready! I just made a few minor adjustments.
You know it happens every day…
The hand is faster than the Multi Box
Don’t you hate when you’re trying to search a string in a Multi Box but you’re faster than QlikView? Usually if you start typing before the Multi Box loads, this happens:
There is a natural instinct in every IT specialist that dictates that if you can’t figure out what the problem is, you should reboot the system.
When QlikView Server is acting weird I usually restart all its services but sometimes it takes a couple of seconds to restore the whole system. In this lapse, the console shows this blood-freezing crimson label. Longest 30 seconds of your life.
Set Analysis Syntax
Why? Just… why?
Do you struggle with any other features? Please share your ideas in the comments section!