{"id":38294,"date":"2018-11-22T12:30:32","date_gmt":"2018-11-22T07:00:32","guid":{"rendered":"https:\/\/data-flair.training\/blogs\/?p=38294"},"modified":"2021-12-07T11:19:51","modified_gmt":"2021-12-07T05:49:51","slug":"qlikview-direct-discovery","status":"publish","type":"post","link":"https:\/\/data-flair.training\/blogs\/qlikview-direct-discovery\/","title":{"rendered":"QlikView Direct Discovery – Working & QlikView Data Query"},"content":{"rendered":"

In our last tutorial, we talked about QlikView T-Test<\/a>. Here, we will learn about What is QlikView Direct Discovery.<\/p>\n

Moreover, we will discuss field types and variables of Direct Discovery in QlikView. In addition, we study the QlikView Direct Query and\u00a0QlikView Direct Discovery Data Model Vs\u00a0In-Memory.<\/p>\n

The term Big Data<\/a> has been creating a buzz since quite some time now and all the new Business Intelligence tools<\/a> focus on analyzing big data.<\/p>\n

In QlikView also, big data or large amounts of data from external data sources can analyze along with other kinds of data through a script-based feature known as Direct Discovery<\/strong>.<\/p>\n

So, let’s start QlikView Direct Discovery.<\/p>\n

\"QlikView<\/a>

QlikView Direct Discovery – Working & QlikView Data Query<\/p><\/div>\n

What is QlikView Direct Discovery?<\/h3>\n

Direct Discovery is a unique concept of hybrid data analysis. Traditionally, in QlikView, in-memory data is the main source of data to use for business analytics.<\/span><\/span><\/p>\n

However, we know that having only in-memory data as the main source of data is not enough. This inefficiency of the software counter by Direct Discovery<\/strong> feature which lets the user access the ocean of information in the form of data.<\/span><\/span><\/p>\n

Also, what enhances the business of an enterprise is how well are they able to keep up with the new trends in business and maintain their market value.<\/span><\/span><\/p>\n

Direct Discovery achieves by analysing as much relevant data as possible in order to get closest to what is happening in the real world. <\/span><\/span><\/p>\n

QlikView enables this by the Direct Discovery feature through which a user can fetch data from both in-memory and external databases (big data) and use this data as a single data set in a document.<\/span><\/span><\/p>\n

The QlikView Direct Discovery follows a query model and both, in-memory data and external database data follows the associative model of QlikView once loaded. <\/span><\/span><\/p>\n

However, one common challenged faced every time a software gets to deal with big data is its volume and variety.<\/span><\/span><\/p>\n

Do you know what is the best practice for Data Modeling in QlikView?<\/a><\/p>\n

This problem solves as direct discovery is a query-based approach where queries send to retrieve and store only some part of the big data into the QlikView\u2019s memory keeping the rest at the source. <\/span><\/span><\/p>\n

QlikView Direct Discovery provides a great deal of transparency and lets any type of user get access to the big data along with in-memory data to use them together for business analysis. <\/span><\/span><\/p>\n

This also alleviates the issue of data silos.<\/span><\/span><\/p>\n

QlikView Direct Discovery Field Types<\/h3>\n

The QlikView Direct Discovery table structure has data fields of three types;<\/span><\/span><\/p>\n

a. Dimension Fields<\/h4>\n

The Dimension<\/a> fields have the descriptive texts defining the values contained in that field. The dimension fields load and define by the keyword DIMENSION in the script<\/a>. <\/span><\/span><\/p>\n

These fields are the only fields that load in memory during direct discovery from the external database and also use in establishing associations between in-memory data fields\/field values and direct discovery fields and values. <\/span><\/span><\/p>\n

b. Measure Fields<\/h4>\n

Entirely different from the dimension field, the Measure fields only contain numeric values upon which calculations are to perform using aggregation functions.<\/span><\/span><\/p>\n

Aggregation functions<\/a> like Sum, Min, Max, Avg, Count use on the data values in measure fields. The measure fields do not load into in-memory indirect discovery tables.<\/span><\/span><\/p>\n

This is because the aggregate functions apply at the database level and do not occupy the in-memory in applying aggregation on data. <\/span><\/span><\/p>\n

c. Detail Fields<\/h4>\n

The detail fields are simple fields that contain descriptive and important comments or remarks on the data being used. <\/span><\/span><\/p>\n

The data in detail fields do not use as dimension or measure. Hence, in any expression. Any field can designate as a Detail field using the keyword DETAIL.<\/span><\/span><\/p>\n

The table given below shows some characteristics of the three field types.<\/span><\/span><\/p>\n\n\n\n\n\n<\/colgroup>\n\n\n\n\n\n
Field Type<\/strong><\/td>\nIn-Memory?<\/strong><\/td>\nForms\u00a0 Association?<\/strong><\/td>\nUsed in Chart Expressions\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/strong><\/td>\n<\/tr>\n
DIMENSION\u00a0 \u00a0\u00a0<\/strong><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\n<\/tr>\n
MEASURE\u00a0 \u00a0 \u00a0 \u00a0<\/strong><\/td>\nNo<\/td>\nNo<\/td>\nYes<\/td>\n<\/tr>\n
DETAIL\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/strong><\/td>\nNo<\/td>\nNo<\/td>\nNo<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

QlikView Direct Discovery Variables<\/h3>\n

There are certain dedicate variables use in direct discovery statements. In this section, we are going to learn different types of\u00a0QlikView direct discovery variables based on the purpose of the action they perform.<\/span><\/span><\/p>\n

a. QlikView Direct Discovery System Variables<\/h4>\n