QlikView Access Point allows users to interact with apps in their browser. But what if those users are not on your domain or only require static data? How can we get information to them in a way that is robust and cost effective?
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.
QlikView is, of course, my software of choice. However, I would not want to be going on client site to do a job without some other tools in my kit bag. Read on to find out the tools I use. Which of these do you use? What other tools should I consider?
Recently I blogged on Include Files in QlikView, and mentioned the fact that QlikView doesn’t advise you when an include file was missing. This led to a discussion on QlikCommunity and a revelation to me of a new feature. This feature is not documented in the QlikView help files and Google turned up just one result for it.
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..
This is another tale in the series of stories from the coalface of QlikView consultancy. This time it’s a story of what can happen when organic growth of applications occurs unchecked. It is also a warning.
When developing QlikView apps it is a good idea to develop standards that you adopt across all of your documents. A good way of ensuring these standards are followed is to use Include files in your load scripts.
QlikView Include files are snippets of code that are stored as text files outside of the QlikView app. Use of includes across multiple apps allows for effective code reuse.
In previous articles I have mentioned how critical it is to ensure your loads from QVD are optimised, but have not gone into the detail of how to do this. This post rectifies that. Here I explain what an optimised load is, why you should use them and how to perform them.
Analysis in QlikView is lightening quick, millions of rows can be aggregated and manipulated with very little latency. Getting those millions of records off a server elsewhere on your network – now that can be a different matter. This is where a robust QVD strategy and QlikView Incremental Loads become crucial.
QlikView is a tool that is enterprise ready and able to step up to those really big BI projects. One of the pitfalls though is to miss the tactical wins you can have with it and get bogged down working towards a management information utopia.