Support Portal ContactGet in touch

How to add a new Datasource to our Qlikview Application.

   Words by CRM Consultancy

   on 19/04/2017 18:00:00

Qlikview Apps pull data from different locations to build associations in that data and then present the data as a new Dashboard – this article is aimed at providing a step-by-step introduction to how we can get started with Qlikview and writing basic script to read a particular source of data, and then for the script to define which Fields to read into the Qlikview Application.

To do this we can use the following steps:

1. Edit Script - Open the File Menu and click the ‘Edit Script’ option.

2. Script Editor - This opens the Qlikview Script Editor where as develop scripts to read data into the App.

3. New Tab - For a new Datasource we typically want to add a new Tab into the Script so the code for reading the Data is kept separate from other code within the Script. (Separation of Concerns)

To do this we can click the Tab Menu and ‘Add Tab’


After providing a Name for our New Tab, this will add the Tab into the Script for us to add our code into.

4. Connect to a Datasource - There are then various methods we might add as new code for reading Datasources, but to use a simple example, we can connect to a Qlikview Table File.  This is done by clicking the ‘Table File’ option in the Script Editor.


This launches a Wizard where we can select the Qlikview Table File, specify that this is a QVD Table File (as opposed to XML, HTML or other file-based Datasource), and specify a Condition if applicable or simply SELECT all data if not.

At the end of this Wizard, this will then show us the Code that the Wizard is intending to add into our Tab:


Clicking ‘Finish’ then adds this code to our Script and we are ready to go.

5. Edit the Code – now we have code to read the Data back from our Datasource.  However this will initially read ALL the Columns and parse these using the Raw Column Names, which is usually less than ideal, as we may only want certain Named Columns to be available to the Dashboard for easier Development and Design.

To remedy this, we can select all the excess columns brought from the Datasource into the Code, dropdown the Edit Menu and click ‘Comment’ – this comments out the excess fields we may not need or want within our Dashboard.

With our remaining useful fields, we would then typically Alias these fields so they have meaningful Names in our Dashboard – this is done using standard SQL Notation for ‘rawfieldname AS [Formatted Name]’.


6. LOAD – with this code in place, we can click Load for Qlikview to suck the data into our Dashboard. 

Typically we may see an Error here if our Code has a Typo or any malformed script, but otherwise this will pull the data in and get ready for use in the Qlikview Designer.  This will also show us the Number of Lines (i.e. Records) read for each part of our Script, which typically would be each Tab within our Script.



7. Getting Started with the Designer – to get started our initial port of call may be to create a new List Box to act as a Selection in our Dashboard.

This can be done from the Toolbar and then selecting one of our Fields to act as the Selector in the Listbox.


This adds a Selector to our Dashboard to filter the Records we are Reporting on by the User’s Selection.

If we tick the ‘Show Frequency’ and ‘Show Percent’ Checkboxes for the List Box, this also acts to show the % of records that meet that Selection:


This immediately starts giving some use to the Dashboard as the user can see the Ratio or Number of records for each possible Selection.

This concept of associations in the data for different selections is at the heart of Qlikview, and so gets us started to build Interactive Contextual Dashboards in Qlikview.

Next Step?  Getting stuck into the Designer to see how we can present our Dashboard, which will form our next How-to article on Qlikview.

Share this Article

Search Articles

Filter Articles

CRM Tech DocMan

Recent Articles

CRMCS Quick Start Guide: How To Produce a Microsoft Teams Live Event Dynamics 365 Marketing: Lead Scoring and Sales Acceptance Designing and Developing Microsoft Power Apps Portals Thank You for Attending CRMCS’ Webinar - Achieving B2B sales excellence with Dynamics 365 & Microsoft Teams Thank You for Attending Our Webinar - Achieving B2B sales excellence with Dynamics 365 & Microsoft Teams Webinar: Discover How CRMCS Have United Dynamics 365, SharePoint and Microsoft Teams To Create Sales Excellence Ignite your workflow by adding DocDrive365 to Office 365 The CRMCS guide to everything you need to know about integrating Teams with Dynamics 365 Saving Time By Keeping Documents In One Place TDE Database Encryption with On Premise Dynamics The Key to Successful Compliance in 2020 Part 2: Let’s get GDPR Compliant with Microsoft Power Automate Top 3 Essential Tips for Remote Working Dynamics 365 Marketing: Top 5 Best Features Dynamics Day in the Life - Puma Investments Can you use Teams to amplify collaboration in Dynamics? Part 1: Using a Scheduled Power Automate to Trigger Expiry Date Reminders The secrets of successful document collaboration in Dynamics CRMCS launches new AppSource approved DocDrive365 Dynamics Day in the Life - Moneypenny Release Management Add the App to Dynamics DocDrive365 Security: Day One - Getting Started with Dynamics to SharePoint Permissions Building a New Scheduled Process using Flow
  • "Paul has made a real difference to how my team of 24 people record and store valuable customer data and sales opportunities. Highly recommended."

    James, Operations Director

  • "Understanding your business allows us to advise when to implement aspects of CRM and, likewise, when not to."

    Paul McQuillan, Managing Director

  • "Dynamics 365 and CRMCS have made a real lasting difference to our business, allowing us to replace older systems that were holding back our performance."

    Grahame, Chief Operating Officer

  • "James worked well with us to help connect CRM with Outlook and relate how this might benefit our team using CRM for Property Care."

    Natalie, Property Care Supervisor

  • "Matt was really good with helping us run User Testing on the new Compliance Module of our CRM System."

    Tom, Compliance Administrator

Prefer to go old-school?

Write to us using the below addresses.

Head Office
CRM Consultancy
61 Oxford Street
M1 6EQ

London Office
CRM Consultancy London
Grosvenor Avenue

Content © CRM Consultancy.