You might think that there is not much to say about buttons in QlikView. If so you are probably not thinking much beyond a shiny lozenge of a thing that invites you to Clear Current Selections. I’m here to convince you otherwise.
Captions on charts and tables are quite useful in QlikView, the colouring of the caption can denote currently selected objects and the caption provides an anchor to pick up and move objects by. If you are going to have captions then you should at least use them well. How? Read on..
In this blog post I want to suggest that you show your users the raw data in your source systems, without modification. Not just some of it – but as much of it as your hardware can manage.
As you probably already know as your reading this; QlikView has an incredibly rich palette of design options. Your data can be surfaced and presented in all manner of ways with pizzazz – making it leap off the page and demand to be noticed. However, not all attention is good – if your latest chart creation is noticed only for its dizzying array of colours then it is likely that the insight in the numbers will have been lost.
The QlikCommunity is a fantastic resource for QlikView developers and users alike. It allows members to post questions and get quick results relating to anything to do with QlikView.
I contribute whenever I can to this forum, providing solutions to users development issues. Sometimes descriptions are not enough and the best way to help is to upload a working example. That is one of the reasons QlikCommunity has a Shared QlikViews section.
There have been a number of articles recently about the significance of colour within the QlikView universe [see Green is the Colour]. The branding and strong message of selection of the Green, the association of the items shown in White and the valuable otherwise hidden insights that can be found in the Grey. These three colours are part of what makes the QlikView user experience so engaging and easy to pick up.
A while back I blogged on What Makes A QlikView Developer, and the large number of different skills an individual needs to excel at providing business insight using QlikView. However, even the most highly skilled individual is not going to be able to make an entire QlikView project work on their own. By its very nature QlikView sits in the middle of an ecosystem made up of people with very distinct needs bringing a number of different skills.
Recently I blogged on the pitfalls of not investing sufficient effort at the start of a QlikView project to avoid problems later on (see the post Start Your QlikView Project The Right Way). In this article I advised that the single most significant factor in whether a QlikView project is a success is a well designed data model. Here I would like to share some of my suggestions for getting the data model right, as this could save you a lot of pain if you are just about to build a QlikView Document or indeed a whole environment.
As a freelance QlikView consultant I can be drafted in at any stage of a QlikView implementation. My favourite sites tend to be the ones where I come in and do the initial demo to the client (not least because I love seeing the moment when jaws drop in the demo) and then build the solution from the ground up. Often though I am called in where a lot of effort has been expended already but things have got to a sticking point and someone decides expert help is required.
One of the things QlikView is great at is dashboards. In fact the word Document and Dashboard seem to have become interchangeable when talking about QlikView files – even when the content is in no way a dashboard. Why is this?