Few months back, I got an opportunity to work on a QlikView project with an insurance company. The objective was to create a sales dashboard to bring out business insights, which could help improve sales of the company. Needless to say, the dashboard required use of multiple metrics and dimensions.
One of the common ways to include multiple dimensions in QlikView is to arrange them using list boxes. While this simple approach works, it ends up taking a lot of space in the dashboard. This leads to lesser area being available to represent your information. In this situation, how do you accomplish the task? Some challenges were associated with this project as discussed below:
There are multiple ways to overcome these challenges. I’ll discuss two such methods in this article:
Let’s look at both the options in detail.
Let’s look at the pre and post effect of this method on sheet space in QlikView (refer to the snapshot below):
Did you notice the difference in the two snapshots? Snapshot at the right has more space available for effective data representation. How did we manage to get this extra space? How did we reduce the number of list boxes?
Well…this isn’t rocket science! If you observe closely, you will notice three new sub tabs appearing on top left corner: “Policy“, “FPA” and “SM“. We have simply categorized the dimensions in three categories and enabled them conditionally.
Let’s look at the steps to perform this:
Step-1: Create a variable “Var_Active” and assign it the value 0 (zero). Go to Settings Menu –> Variable Overview. Then, click on ADD button to create new variable.
Step-2: Categorize the dimensions, identify the number of unique categories and create text boxes for each one. Here we have three different categories as Policy, FPA and SM represented by three text boxes.
Step-3: Set ‘action’ for all three text boxes to assign the unique value to variable “Var_Active“. This is how you can do:
Select Text box –> Go to properties –> Actions Tab –> Click on ADD –> Select “External” action type and “Set Variable” as an action parameter. After that put the “Var_Active” in variable box and assign unique value for Value text box as 0.
Similar steps can be performed for FPA and SM text box also. Simply, assign unique value 1 for FPA and 2 for SM.
Step-4: Select list boxes individually and apply condition enable option using unique value of their respective category. Below are the steps:
Select List box (Branch City) –> Go to Properties –> Layout Tab –> Option button on for “Conditional Show” –> Put expression “Var_Active=0“. Here, we have assigned value ‘0’ to ‘Var_Active’ as it belongs to category ‘Policy'(value for Var_Active is set at ‘0’).
Similarly, we can do it for other list boxes and assign respective variable value based on their category.
Step-5: This is an optional step. It enhances the visual effect. When we select a text box, it’s color changes, which indicates it as an active category. Below are the steps to do it:
Select text box (Policy) –> Go to properties window –> General tab –> Click on color button –>Select calculated option under base color bucket. Then, write the expression as: “=If(Var_Active=0,rgb(0,128,0),rgb(214,231,248))”.
This expression can be read as: If variable value is ‘0’ then color should go as green else default color. Similar expression can be written for other text boxes also. Only conditional argument will change as “Var_Active=1″ for FPA and “Var_Active=2″ for SM.
Now, we have sub tabs for list boxes seen as Policy, FPA and SM. It will show list boxes related to the active category. Similarly, we can use command button to perform this conditional enable or disable list boxes. This feature can also be used with chart objects.
QlikView has another object that can be used to show multiple chart objects at the same place where charts objects can be accessed using tabs known as CONTAINER.
Container is a QlikView object which holds multiple charts in the same box as seen below. All charts will appear in the same window but only one chart will appear active at a given time and navigation to different charts can be done using the bottom tabs. Position of the tabs can be changed to top, left and right as well. Look at the snapshot below, here we have four different charts namely Region wise sales, Region wise Profit, Manpower Distribution, YoY Growth available in one container. Users can navigate through the charts by clicking on their respective tabs.
Method to create container is as easy as drag and drop objects. It is just a two steps process. Let’s take a look:
Select Container from ‘New Sheet Object List’ –> Select objects from list of available objects on ‘General’ tab. Now, we have Container with selected list of objects. We can change the position of tab or container type by selecting different option under ‘Presentation’ tab.
In this article, we have looked at two methods for effective use of sheet space:
These two techniques are quite effective in utilizing your sheet space. Have you used these techniques ever while working on QlikView? Do yo know of any other hacks to utilize sheet space effectively? Share your valuable experience with our readers through comments below.
Sunil Ray is Chief Content Officer at Analytics Vidhya, India's largest Analytics community. I am deeply passionate about understanding and explaining concepts from first principles. In my current role, I am responsible for creating top notch content for Analytics Vidhya including its courses, conferences, blogs and Competitions.
I thrive in fast paced environment and love building and scaling products which unleash huge value for customers using data and technology. Over the last 6 years, I have built the content team and created multiple data products at Analytics Vidhya.
Prior to Analytics Vidhya, I have 7+ years of experience working with several insurance companies like Max Life, Max Bupa, Birla Sun Life & Aviva Life Insurance in different data roles.
Industry exposure: Insurance, and EdTech
Major capabilities: Content Development, Product Management, Analytics, Growth Strategy.
Open-Source BI Tool Metabase for Data Visualiza...
10 Ultimate Tips and Tricks on Data Visualizati...
Data Visualization for Tabular Information (wit...
Customized Reporting in Qlikview
Creating a simple and effective Sales dashboard...
Use of variables in QlikView to create powerful...
Creating a simple and effective Sales dashboard...
Tips for creating a winning dashboard
How to create Box-Plot chart in Qlikview?
Data Visualization: Creating Geo-spatial dashbo...
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
It is needed for personalizing the website.
Expiry: Session
Type: HTTP
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Expiry: Session
Type: HTTPS
Preserves the login/logout state of users across the whole site.
Expiry: Session
Type: HTTPS
Preserves users' states across page requests.
Expiry: Session
Type: HTTPS
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
Expiry: 365 days
Type: HTTP
Used by Microsoft Clarity, to store and track visits across websites.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
Expiry: 1 Day
Type: HTTP
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Years
Type: HTTP
Use to measure the use of the website for internal analytics
Expiry: 1 Years
Type: HTTP
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
Expiry: 1 Year
Type: HTTP
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Months
Type: HTTP
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics, to store and count pageviews.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
Expiry: 1 Day
Type: HTTP
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
Expiry: Session
Type: PIXEL
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
Expiry: 6 Months
Type: HTTP
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
Expiry: 2 Years
Type: HTTP
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
Expiry: 1 Year
Type: HTTP
this is used to send push notification using webengage.
Expiry: 1 Year
Type: HTTP
used by webenage to track auth of webenagage.
Expiry: Session
Type: HTTP
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
Expiry: 1 Day
Type: HTTP
Use to maintain an anonymous user session by the server.
Expiry: 1 Year
Type: HTTP
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
Expiry: 1 Year
Type: HTTP
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
Expiry: 6 Months
Type: HTTP
allow for the Linkedin follow feature.
Expiry: 1 Year
Type: HTTP
often used to identify you, including your name, interests, and previous activity.
Expiry: 2 Months
Type: HTTP
Tracks the time that the previous page took to load
Expiry: Session
Type: HTTP
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
Expiry: Session
Type: HTTP
Tracks percent of page viewed
Expiry: Session
Type: HTTP
Indicates the start of a session for Adobe Experience Cloud
Expiry: Session
Type: HTTP
Provides page name value (URL) for use by Adobe Analytics
Expiry: Session
Type: HTTP
Used to retain and fetch time since last visit in Adobe Analytics
Expiry: 6 Months
Type: HTTP
Remembers a user's display preference/theme setting
Expiry: 6 Months
Type: HTTP
Remembers which users have updated their display / theme preferences
Expiry: 6 Months
Type: HTTP
Used by Google Adsense, to store and track conversions.
Expiry: 3 Months
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 6 Hours
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 1 Month
Type: HTTP
These cookies are used to gather website statistics, and track conversion rates.
Expiry: 1 Month
Type: HTTP
Aggregate analysis of website visitors
Expiry: 6 Months
Type: HTTP
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
Expiry: 4 Months
Type: HTTP
Contains a unique browser and user ID, used for targeted advertising.
Expiry: 2 Months
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 1 Year
Type: HTTP
Used by LinkedIn for tracking the use of embedded services.
Expiry: 1 Day
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 6 Months
Type: HTTP
Use these cookies to assign a unique ID when users visit a website.
Expiry: 6 Months
Type: HTTP
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
Expiry: 6 Months
Type: HTTP
Used to make a probabilistic match of a user's identity outside the Designated Countries
Expiry: 90 Days
Type: HTTP
Used to collect information for analytics purposes.
Expiry: 1 year
Type: HTTP
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
Expiry: 1 Day
Type: HTTP
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.
Edit
Resend OTP
Resend OTP in 45s
Good tricks! w.r.t first trick we need to overlap the list boxes else it would look weird, when it comes to container i would keep same container next to each other(duplicating)..so that two charts comparison is possible. In the above example if we duplicate the container, comparison of region wise sales with that of profit would be easy.
you have a good article on QlikView but where practical examples 20-30 lines?
Good tips indeed. Apart from conditional listboxes I also use multibox at times to save some real estate. However, I would go easy on containers if the charts have lot of calculations. Unlike other objects, containers force all the child objects do calculations when the container is activated (even though only one object is active at a time) - which is a pity. Also, if u put a container within another, your objects in IE Plugin access point may behave weird.