Book Image

QlikView: Advanced Data Visualization

By : Miguel Angel Garcia, Barry Harmsen, Stephen Redmond, Karl Pover
Book Image

QlikView: Advanced Data Visualization

By: Miguel Angel Garcia, Barry Harmsen, Stephen Redmond, Karl Pover

Overview of this book

QlikView is one of the most flexible and powerful business intelligence platforms around, and if you want to transform data into insights, it is one of the best options you have at hand. Use this Learning Path, to explore the many features of QlikView to realize the potential of your data and present it as impactful and engaging visualizations. Each chapter in this Learning Path starts with an understanding of a business requirement and its associated data model and then helps you create insightful analysis and data visualizations around it. You will look at problems that you might encounter while visualizing complex data insights using QlikView, and learn how to troubleshoot these and other not-so-common errors. This Learning Path contains real-world examples from a variety of business domains, such as sales, finance, marketing, and human resources. With all the knowledge that you gain from this Learning Path, you will have all the experience you need to implement your next QlikView project like a pro. This Learning Path includes content from the following Packt products: • QlikView for Developers by Miguel Ángel García, Barry Harmsen • Mastering QlikView by Stephen Redmond • Mastering QlikView Data Visualization by Karl Pover
Table of Contents (25 chapters)
QlikView: Advanced Data Visualization
Contributors
Preface
Index

Design requirements


When we start building the frontend of a QlikView document, we should always begin by defining two fundamental characteristics:

  • The screen resolution on which most users will access the document

  • The general style and layout of the document

We need to set a standard screen resolution right from the start because it will ultimately determine the placement and size of the objects across the screen. If we build the document targeting a screen resolution higher than that which users have on their machines, they will probably need to use the scroll bars too often. On the other hand, if we target our document to a screen resolution lower than our users' screen resolution, they will see a lot of empty space. Both of these situations will be an inconvenience that our users will need to deal with every day, so we don't want that to happen.

Note

Having a predefined resolution in the document does not keep the user from accessing a document using a lower (or higher)resolution monitor...