Introduction
QlikView is an innovative platform to present the data in business discovery. QlikView is quite good in real life. But there is a problem with the representation of the data. QlikView users have the responsibility to get things right every time. In QlikView it is more important to represent data accurately. The QlikView is a user friendly tool. The developers develop the data accurately depending on our application, but there is the problem that the results are answers to the wrong questions. The data integrity check is most important before presenting the application but the developers never perform the data integrity check. So there is generating a problem with QlikView application.
There are given mainly 7 basic steps that cover the most critical items in a QlikView application before presenting the QlikView application results.
Perform Aggregation on main Fact Table
It is the first check. Mostly you saw in a QlikView application the incremental load deals with the "Where" clause. When we build the Where clause so there is an error generated, in other words logical error. To remove the logical error, we need to check the row and total of measures fields by comparing them with the underlying source table. We can use system fields like $Field, $Table, $Row and so on.
Not applying aggregation on key fields
In QlikView, key fields are used as a Join key. The developers use "HidePrefix" along with the SET variables and use the some special char or symbol as the prefix before the field name. From this help the developer does not use this field automatically. The developer will not use the key field as the chart dimension.
Example
Use %PersonId instead of [Person Id])
Check for connection strings in QlikView application
Logical errors are very complicated, in other words not easy to find easily. In most of the cases the user extracts data from more than one source. Sometimes the user extracts the data from multiple environments where the existing schema will be the same and same table same.
Example
Suppose a single user extracts the data from a Dev and QlikView application and there is the same schema and same table name but the data is different. So in this situation everything is right in your source code except that you are using an old connection string. So you need to manage the connection string to Excel files and the database to manage them in one place.
There is no syntax error
It is one of the most important test techniques of application either it is QlikView application. Remember always that there is no syntax error in the QlikView application because if there is a syntax error then surely there will be logical error. Logical errors are more complex compared to syntax errors. Set Analysis is the main feature of QlikView. The Set Analysis is very useful to control, modify and identify the data.
Syntax errors are those errors caused by the wrong syntax written in a logical program whereas logical errors are those errors caused by improper logic in code for any operation execution.
Check intruders in the dimensional tables
As per the rulea, in dimensional tables the null values are not allowed. You would always expect that the dimensional table have 100% information density.
Check for information density
The information density shows the percentage of rows in the table with values.The information density is always 100%. The information density is the number of records that have values except Null values in the field as compared to the total number of records in the table. You can view the information density from the Table viewer in the toolbar. If the information density is 100% then it is fully satisfied and if it is less than 100% then it should have Null values.
Check for Subset ratio
The Subset ratio performs the percentage of distinct values in this table for this data field. The information density is the number of distinct values of this field found in this table as compared to the total number of distinct values of this field. You can also view the Subset ratio from Table viewer option in the toolbar.
Summary
This article described the basic procedure for testing our QlikView application.