A REPORT SUBMITTED IN PARTIAL FULFILMENT OF

THE REQUIREMENT OF UNDER GRADUATE DEGREE

IN ENGINEERING (2021-2025)

Submitted By:
Atul Pandey

Guided By:

Mr. M Surya Rao, Head of Department, IT Dept.

Harishankar Dewangan, Asst. Manager (Data Analytics), IT Dept.

Submitted To:
HR DEPARTMENT, JINDAL STEEL & POWER,
RAIGARH 2022-2023
 CERTIFICATE FROM FACULTY MENTOR

This is to certify that Mr. Atul Pandey Roll No.2101010235 a student of

Btech (2021-2025) has worked on a project titled “Data Analysis:
JSPL”, towards the partial fulfilment of the requirements for the degree
of Bachelor of Business Administration programme at Bhilai Insititue of
Technology, Durg.
This is her original work to the best of my knowledge.

(Signature of the faculty mentor)

PROF. BISWAJIT ACHARJYA
 CERTIFICATE

This is to certify that this report for internship is record of bona fide work, carried
out by Mr. Atul Pandey under the guidance of Mr. M Surya Rao (HOD, IT
Department, JSPL) & Mr. Harishankar Dewangan (Assistant Manager,
Analytics, IT Department, JSPL) at Jindal Steel & Power. A REPORT
SUBMITTED IN PARTIAL FULFILMENT OF THE REQUIREMENT OF
UNDER GRADUATE DEGREE IN MANAGEMENT as per the regulations of
the Jindal Steel & Power Limited. To the best of my knowledge, the results
embodied in this report, are original in nature and worthy of incorporation in the
present version of the report.

Mr. M Surya Rao Mr. Harishankar Dewangan

Head of Department Asst. Manager, Analytics
IT Department IT Department
Jindal Steel & Power, Raigarh Jindal Steel & Power, Raigarh
 ACKNOWLEDGMENT

The achievement that is associated with the successful completion of any task
would be incomplete without mentioning the names of those people whose endless
cooperation made it possible. Their constant guidance and encouragement made all
our efforts successful. We take this opportunity to express our deep gratitude
towards Mr. M Surya Rao, Head of Department, for allowing me to do the
training and Mr. Harishankar Dewangan, Asst. Manager, for giving such valuable
suggestions, guidance and encouragement during the time period of training. Last
but not the least we are grateful to all the members of Jindal Steel and Power for
their support and resources.
TABLE OF CONTENT

1. Introduction
2. App Overview
3. Sheet View
4. Visualizations
5. Selections
6. Selection Sheet
7. Connecting to Data Sources
8. Viewing the Data Model
9. Script Statements & Keywords
10. Script Control Statements
11. Visualization Expressions
12. Functions & Statements Not Recommended in Qlik Sense
13. Snapshots
14. References
 Introduction
Qlik Sense is a data visualization and discovery product that allows you to create
flexible, interactive visualizations that lead to meaningful decisions.

Most Business Intelligence (BI) products can help you answer questions that are
understood in advance. But what about your follow-up questions? The ones that
come after someone reads your report or sees your visualization? With the Qlik
Sense associative model, you can answer question after question, moving along
your own path to insight. With Qlik Sense you can explore your data freely,
learning at each step along the way and coming up with next steps based on earlier
findings.

Qlik Sense responds instantly as you work. Qlik Sense does not require predefined
and static reports, and you do not need to depend on others. Just click and learn,
while Qlik Sense updates every visualization and view in the app with a newly
calculated set of data and visualizations specific to your selections.
 App Overview

Click the app Beginner’s tutorial. The app overview is opened, and you can see the
content of the app
By default, the app overview shows the sheets of the app. In the Beginner’s
tutorial app there are four sheets, Dashboard, Product Details, Customer Details,
and Customer Location. You do most of the work in the sheets, especially if you
are primarily a business user and not a developer. Click Dashboard to open that
sheet.
App overview displaying the sheets of the app.

Sheet View
You explore, analyze, and discover the data in the sheets. This is also where you
create, design, and structure the visualizations when you build apps.
The sheet view has three sections: the toolbar, the selections tool, and the sheet.
When you are editing a sheet there are panels on both sides of the sheet, but they
will not be used in this tutorial.
Sheet view in an app

The following table presents the main parts of the sheet.

Main areas of sheet view

UI item Description

A: The toolbar The toolbar contains options to navigate in your

sheet and app.

B: The selections The selections bar contains options to make

bar selections in your data and to clear those selections,
and to search for data.
The selections tool also displays all selections that
have been made.

C: The sheet The sheet is where you interact with the

visualizations.
Main areas of sheet view

UI item Description

D: Take snapshot, Take a snapshot of your chart, change certain chart

exploration menu, properties in the exploration menu, or view your
full screen chart in full screen mode. Hover over a chart to view
the menu.

Options menu
Right-click on a chart to view the options menu.
All of the options may not be available depending on whether you are editing or
analyzing (viewing) charts in an app, and depending on the privileges that have
been assigned to you by your administrator.
Options menu

The menu will look different if you have touch screen mode enabled on a
supported device. You can disable touch screen mode in the global menu.
 Visualizations

Before you start working with Qlik Sense, it is a good idea to get an understanding
of the basics of visualizations.

Measures and dimensions

A visualization consists of at least one measure or one dimension. In most cases a
visualization has both, and sometimes more than one dimension or measure.
Dimensions determine how the data in a visualization is grouped. Dimension
values often refer to time, place, or category.
Measures are the result of some sort of calculation, often aggregations, such
as Sum, Count, or Avg (average).
When dimensions and measures are combined in a visualization, it is possible to
see, for example, how many bikes of a certain category were sold in a certain area
during a certain period of time.

Dashboard visualizations
Different visualizations serve different purposes. The point of a visualization in
general is to communicate its data in a quick and meaningful way while remaining
100% accurate.
Let us have a look at the visualizations in the app.
Dashboard sheet with different visualizations.

Filter panes
In the sheet Dashboard, there are two filter panes to the left: the time filter pane
without title and Region. They are both filter panes, although they do not look the
same. Region contains only one dimension, and shows the dimension values in a
list. The time filter pane contains four dimensions, and because the space is
limited, the lists are all compressed to panes. The purpose of the filter panes is to
filter out a limited data set, which you can analyze and explore.

Pie chart
To the right of the time filter pane is a pie chart, Sales per Region. Pie charts show
the relationship between values, as well as the relation of a single value to the total.
Each sector represents a value, and as long as there are a limited number of values
(less than 10), you get a good overview of the relative size of the sectors. The
values are ordered by size.
Bar chart
Below the pie chart is a bar chart, Top 5 Customers. Bar charts are useful when
you want to compare multiple values. The bars give information about the
relationship between different values. Bars can be grouped or stacked, and be
displayed horizontally or vertically.

Combo chart
Beneath the bar chart is a combo chart, Sales Trend. Combo charts are usually used
for displaying trends with bars and lines in the same visualization. A combo chart
is especially useful when you want to combine values that normally are hard to
combine, because they have totally different scales. The solution in the combo
chart is to have two axes for the measures. In Sales Trend, the combo chart
combines sales figures (millions of dollars, on the left axis) with margin (percent,
on the right axis).

KPI
To the right of the pie chart is a KPI visualization, Total Sales and Margin. It can
be very useful to track performance. In a KPI visualization, you can show one or
two measure values with text labels. You can add conditional colors and symbols
to the values.

Gauge
To the right of the KPI visualization is a gauge, Profit Margin. A gauge is used to
display a single key measure value. In this case it is the profit margin. The colors
reinforce the interpretation of the value.

Line chart
The final visualization is a line chart, Quarterly Trend. Line charts are often used
to show trends, and this chart uses two dimensions, year and quarter that displays
the trends for each quarter of the years 2012-2014.

Product Details visualizations

Do the following:

● In the top right corner, click ë to go to the sheet Product Details.

Product Details sheet with different visualizations.

Treemap
The second sheet, Product Details, contains one new visualization type compared
to the sheet Dashboard, and that is the treemap. Treemap are ideal when you want
to display hierarchical data in a limited space. In this treemap the hierarchy
consists of the dimensions Product Group, Product Type, and Item Desc. You start
at the top level (Product Group), and when you make and confirm selections in the
treemap you drill down to the next level (Product Type) to analyze the more
detailed data. The items in the treemap are colored by measure. The darker the
color, the higher the measure value.
The screenshot was taken in an app with reduced sheet width. As a consequence,
the bar chart does not display all values at the same time. Therefore, it has a mini
chart below the bar chart, which shows a miniature of the full chart. The mini chart
has a scroll bar that can be used for navigation.

Customer Details visualizations

Do the following:
 ● In the top right corner, click ë to go to the sheet Customer Details.
Customer Details sheet with different visualizations.

The Customer Details sheet has two new visualizations, a scatter plot, Customer
Sales and Quantity, and a pivot table, Customer KPIs.

Scatter plot
With a scatter plot you can find potential relationships between values, and identify
values that deviate from a group. The size of the bubbles can be used to show
differences in values. In this scatter plot the bubbles show the relationship between
sales and quantity, and each bubble is a dimension value: the customer.

Pivot table
The pivot table Customer KPIs shows key customer figures. You can rearrange
how the data is displayed, and analyze data by multiple dimensions and measures
at the same time to get different views of the data.
Customer Location visualizations
Do the following:

● In the top right corner, click ë to go to the sheet Customer Location.

Customer Location sheet with different visualizations.

Map
The fourth sheet, Customer Location, contains three filter panes and one new
visualization: a map. In Qlik Sense you can create maps that display data in point
layers and area layers. The map we are using in this tutorial contains a point layer.
A point layer is created using point coordinates (latitude and longitude) or location
names to mark places of interest, for example cities.
Maps can, for example, be used for plotting sales data per region or per location.
The map in this tutorial is used to show customer locations. You can filter
by Region, City, or Customer. You can also make selections directly in the map by
clicking on a point. If you hold down Shift before you make a selection you can
select several areas to analyze.
 Selections

When you use an app, you make selections to reduce the data set, so that you can
focus on particular values. You can make selections in almost all visualizations,
and in most cases in many different ways.
Basically, you either click or draw to make a selection. When you click, you select
one value at a time, when you draw, you select many values at a time. All selection
methods are not available for all visualizations, but the variety of options ensures
that you always find a smooth way of making selections.

Click selection
In the following pie chart, the sector Nordic has been clicked and is thereby
selected. The other values are dimmed. You can confirm the selection by
clicking or by clicking outside the visualization.
The sector Nordic has been selected

Draw selection
You can draw a freehand line to select several values at a time. To deselect values,
you click them one at a time. To activate draw selection, either click inside the
visualization and then click , or hold down Shift while you make your selection.
Bar chart with Nordic, USA and Japan selected
In lists and tables, you can draw across several values to select them.
Region filter pane with Germany, Japan and Nordic selected

Range selection
You can make a selection by drawing along the y-axis or the x-axis, just outside
the chart. For an axis showing measure values, you are also able to click on the
range bubble to enter a specific numeric value.
Combo chart with selections made with range selection
Line chart with selections made with range selection

Lasso selection
You can draw a freehand circle to capture and select data points. To deselect
values, you click them one at a time. To activate the lasso selection, either click
inside the visualization and then click , or hold down Shift while you make your
selection.
Selection of values made in a scatter plot using lasso selection
Legend selection
You can click the legend items to select the values.
Pie chart with sectors Nordic, Germany and UK selected

Label selection
You can click the dimension labels (in this example, 2012, 2013, and 2014) to
select the corresponding value. In the example, the dimension values are grouped
so that clicking one of the years for a country automatically selects all the values
for that country.
Bar chart with label selection of 2011, 2012, and 2013. Clicking any of the years
selects the whole group.

Selection States
Now you know how to make selections, but what happens when you make a
selection? Selections filter out a subset of the data that is loaded into Qlik Sense.
You use selections to focus on something you want to know more about.

Green, white, and gray

When you make selections in filter panes, the colors of the values change
accordingly. The characteristic Qlik Sense colors are green, white, and gray, and
they represent the basic states: selected, possible, and excluded. The excluded
values exist in three different variants. In addition to the normal excluded state,
there are also the alternative state and the selected excluded state. These will be
described later.
Colors that are used for different states

State Color

Selected Green, with a check mark as a selection indicator

Possible White

Alternative Light gray

Excluded Dark gray

Selected excluded Dark gray with a check mark as a selection indicator

The whole point behind color coding is to bring you additional information. Green
indicates what has been selected, white indicates the values that are possible to
select, and gray indicates the values that have not been included in your selection.
In particular, the gray values can bring you new information about relationships
that were not known before. When a value unexpectedly turns gray after a
selection it can lead to new insights, for example, that a certain region does not
have any sales representatives, or that a product did not sell at all during a whole
quarter.
Making the first selections
Let us make some selections in the app to get an understanding of the different
states. But first, go to the sheet Product Details. In the top right corner, click and
select the sheet Product Details.
You will compare the sales of a few different product types
in Germany and Japan during 2012.
Do the following:
● In the top left filter pane, click Year and select 2012 but do not confirm the
selection.

When you click 2012 the value turns green to indicate that it is selected. The two
other values, 2013 and 2014, turn light gray to indicate that they are alternative,
which means that they are excluded from the selection. You can select either of the
two if you want to change the scope, but by selecting 2012 you want the other
years to be excluded, because you only want to see values for 2012.
As soon as you make a selection, the other visualizations are updated. You do not
even have to confirm the selection to see the outcome, a preview is shown
immediately. You can undo a selection by clicking .
After the selection of 2012, the filter pane Region does not change. It is still white,
indicating that the values are associated and can be selected. The bar chart Total
Sales is updated to display only the sales for 2012, and, likewise, Product
Treemap shows the product groups that were sold in 2012. You can see the
difference if you click 2012 again to deselect it. When no selection is made, the bar
chart and treemap both display the values for all three years, but when 2012 is
selected, only the values related to that year are displayed.
Do the following:
1. Make sure 2012 is selected.
The selections bar above the sheet shows the new selection. More about that
later.
2. Still in the time filter pane, click Quarter and select Q1. Confirm the
selection.
The new selection is added to the selections bar, and the bar chart and
treemap are updated.

3. So far, you have selected 2012 and Q1. Click Month.

You can see that Jan, Feb, and Mar are possible values (white), whereas the
other months are excluded. This makes sense, because the possible values
are months in the first quarter, which you selected, and you could refine your
selection further by selecting one or two of the possible months. Selecting
all three would not constitute a new selection, because that is equal to
selecting Q1, which has already been selected.

4. Click to leave Month without making any selections.

5. In the selections bar, click to clear the selection of Q1.
The selection 2012 should now be the only selection.

Selecting regions and product types

Let us compare the sales of fresh vegetables in Germany and Japan.
Do the following:
1. In the Region filter pane, select Germany and Japan and confirm.
 2. In the Product Treemap, select Produce and confirm.
3. In the treemap, select the product type Vegetables.
By selecting Vegetables, you exclude the other product
types, Fruit, Specialty, and Packaged Vegetables, which are part of the same
product group Produce, but are not fresh vegetables.
To be able to see the relationship between the two countries, you need to
change sheets.

4. In the top right corner, click to go to the sheet Dashboard.

In the pie chart, Sales per Region, you can see that the sales for 2012 is
almost exactly twice as big in Japan as in Germany.
To instead see the figures for Specialty, which is nuts and almonds, do the
following:
5. In the selections bar, click Product Type to open the list.
6. Deselect Vegetables and select Specialty instead. Confirm.
With this selection, Germany has the highest sales, and therefore that value
is presented first in the pie chart (counting clockwise from 12 o' clock).
Now that you have changed sheets, there are some other things to notice.
The selections in this sheet are exactly the same as the ones in the Product
Details sheet. Selections are global. This means that when you make a
selection in a visualization, the selection is reflected in all related
visualizations, no matter what sheet they are on. Consequently, the
selections bar looks the same when you move between the different sheets.
The selections bar shows all selections regardless of which sheet they were
made on.

7. Go to the sheet Customer Location.

You can see that the regions Germany and Japan are still selected, and that
these are the only areas showing data in the map Location.

The excluded values

When you deselected Vegetables to instead select Specialty, the first four values
are possible values that can be selected.
When Specialty is selected, some values are alternative (light grey) and some are
excluded (dark grey).

Specialty is selected and the following three values are alternative, that is, they are
excluded, but only by the selection of Specialty. The values after Vegetables, on
the other hand, are already excluded by a selection in another list, and are therefore
dark gray.
What would happen if you selected the excluded value Bread?
Do the following:

● In the selections list for Product Type, select Bread.

The value is selected (with a check mark) but remains dark gray, that is, it is
selected excluded. The selection of Bread is not compatible with the already
existing selections. But the value is still selected and will become green if the
selection that excludes it is cleared or if the product group to which it belongs, is
included in the selection.

Selected excluded values become selected

You can make the excluded value Bread become selected by doing one of the
following.
 ● In Product Group, select the value Baking Goods, which is light gray,
alternative.
● In Product Group, clear the selection Produce.

● In Product Type, clear the selection Specialty.

Stepping back in the selection history

What if you want to return to the selection with Vegetables? If you remember all
the selections, the quickest way is perhaps to make the selections again. But with
more complex selections it may be difficult to remember all the selections, and you
could easily overlook something. A safer option in that case would be to step back
in the selection history.
Selection history options in the selections bar

In the selections bar, there are options for stepping back and forward in the
selection history. All the selections you have made during this session are stored
and you can return to them by using the step back and step forward options. It is
not until you have stepped back that you can step forward. By default, you are at
the last step in the selection history and therefore you cannot step forward, because
there is no later step.

Connecting to Data Sources

Qlik Sense lets you to connect to your data, wherever it is stored, with a wide
range of Qlik Connectors and other data connection types. When you create a data
connection it is saved to Qlik Sense, so you can quickly select and load data from
the data sources that you commonly use.

Create a connection
To select data from a data source, you can either create a new data connection or
use a saved data connection. You can create data connections and access your
saved connections from:
● Add data in the data manager.
Add new data to your app quickly and get assistance creating associations.
For more information, see Adding data to the app.
● Data connections in the data load editor.
Select data from a new or existing data connection, or use the script editor to
load data from a data connection. You can also edit existing data
connections.
For more information, see Connect to data sources in the data load editor.
● Data sources in shared spaces in the cloud hub
Add data from a new connection to a shared space. You can also edit
existing data connections.
For more information, see Managing data sources in spaces.
Note:
You can only see and use data connections that you own. You cannot change the
owner of a connection.

Connecting to data sources from a private network

To request data from your data connections through a firewall, you need to add
the DNS name for Qlik Sense Enterprise on Kubernetes and the underlying
IP addresses to your whitelist.
Data connection requests are made
from DNS name: <tenantname>.<region>.qlikcloud.com.
Underlying IP addresses (US):
● 18.205.71.36
● 18.232.32.199
● 34.237.68.254
Underlying IP addresses (EU):
 ● 34.247.21.179
● 52.31.212.214
● 54.154.95.18
Underlying IP addresses (APAC):
● 13.210.43.241
● 13.236.104.42
● 13.236.206.172

Data connection types

Qlik Sense allows you to access your data wherever it resides. The following data
connection types are available with Qlik Sense. You can download connectors
from the qlik.com download site to use with Qlik Sense.
Many of the connectors that access these data sources are built into Qlik Sense,
while others can be added. Each type of data connection has specific settings that
you need to configure.

Data files
Load data from files that you have uploaded to your cloud.
For more information, see Adding data from uploaded data files.
Load data into Qlik Sense Enterprise on Kubernetes from files in NFS networked
drive provisioners.
For more information, see NFS connector.

Database connectors
Connect to an ODBC data source with preconfigured ODBC database connectors.

● Amazon Redshift

● Apache Drill (Beta)

● Apache Hive

● Apache Phoenix (Beta)

 ● Apache Spark (Beta)

● Azure SQL

● Cloudera Impala

● Google BigQuery

● Microsoft SQL Server

● MongoDB (Beta)

● MySQL Enterprise

● Oracle

● PostgreSQL

● Presto

● Snowflake

● Teradata
For more information, see Database.

Essbase
Connect to an Essbase dataset.
To learn more about Essbase, see Essbase connector.

REST
Connect to a REST data source. The REST connector is not tailored for a
specific REST data source and can be use to connect to any data source exposed
through the REST API.
To learn more about Qlik REST Connector, see REST.

Salesforce
Connect to your Salesforce.com account.
For more information, see Salesforce connector.
SAP
Connect to SAP NetWeaver.

● SAP SQL
To learn more about SAP connectors, see Qlik Connector for use with SAP
NetWeaver.

Qlik Web Connectors

Connect to social media or web-based data sources.

● Amazon S3 Metadata

● AYLIEN News

● AYLIEN Text Analysis

● Azure Storage Metadata

● Bitly

● Facebook Fan Pages

● Facebook Insights

● GitHub

● Google AdSense

● Google AdWords

● Google Analytics

● Google Calendar

● Google Drive and Spreadsheets

● Google Search Console

● JIRA

● Mailbox IMAP
● MailChimp

● MeaningCloud

● Repustate

● Sentiment140

● Slack

● SMTP

● Strava

● SugarCRM

● SurveyMonkey

● Twitter

● Watson Natural Language Understanding

● YouTube Data

● YouTube Analytics
 Viewing the Data Model

The data model viewer provides you with an overview of the data structure of the
app. You can preview data in the tables and fields in the data model viewer. You
can also create dimensions and measures on-the-fly.
The data mode displays the data structure of the app.
In the data model viewer, each data table is represented by a box, with the table
name as title and with all fields in the table listed. Table associations are shown
with lines, with a dotted line indicating a circular reference. When you select a
table or a field, the highlighting of associations instantly gives you a picture of how
fields and tables are related. You can search for specific tables and fields by
clicking .
You can change the zoom level by clicking Y, Z or using the slider. Click ü to
restore the zoom level to 1:1.

Toolbar
In the data model viewer, you find the following tools in the toolbar at the top of
the screen:
Toolbar options
Script Statements & Keywords
The Qlik Sense script consists of a number of statements. A statement can be either
a regular script statement or a script control statement. Certain statements can be
preceded by prefixes.
Regular statements are typically used for manipulating data in one way or another.
These statements may be written over any number of lines in the script and must
always be terminated by a semicolon, ";".
Control statements are typically used for controlling the flow of the script
execution. Each clause of a control statement must be kept inside one script line
and may be terminated by a semicolon or the end-of-line.
Prefixes may be applied to applicable regular statements but never to control
statements. The when and unless prefixes can however be used as suffixes to a few
specific control statement clauses.
In the next subchapter, an alphabetical listing of all script statements, control
statements and prefixes, are found.
All script keywords can be typed with any combination of lower case and upper
case characters. Field and variable names used in the statements are however case
sensitive.

Script Control Statements

The Qlik Sense script consists of a number of statements. A statement can be either
a regular script statement or a script control statement.
Control statements are typically used for controlling the flow of the script
execution. Each clause of a control statement must be kept inside one script line
and may be terminated by semicolon or end-of-line.
Prefixes are never applied to control statements, with the exceptions of the
prefixes when and unless which may be used with a few specific control
statements.
All script keywords can be typed with any combination of lower case and upper
case characters.
Use the drop-down on each function to see a brief description and the syntax of
each function. Click the function name in the syntax description for further details.
Call
The call control statement calls a subroutine which must be defined by a
previous sub statement.
Call name ( [ paramlist ])

Do..loop
The do..loop control statement is a script iteration construct which executes one or
several statements until a logical condition is met.
do [ ( while | until ) condition ] [statements]
[exit do [ ( when | unless ) condition ] [statements]
loop [ ( while | until ) condition ]

Exit script
This control statement stops script execution. It may be inserted anywhere in the
script.
exit script[ (when | unless) condition ]

For each ..next

The for each..next control statement is a script iteration construct which executes
one or several statements for each value in a comma separated list. The statements
inside the loop enclosed by for and next will be executed for each value of the list.
For Each var in list

[statements]

[exit for [ ( when | unless ) condition ]

[statements]

next [var]

For..next
The for..next control statement is a script iteration construct with a counter. The
statements inside the loop enclosed by for and next will be executed for each value
of the counter variable between specified low and high limits.
Forcounter = expr1 to expr2 [ stepexpr3 ]

[statements]

[exit for [ ( when | unless ) condition ]

[statements]

Next [counter]

If..then
The if..then control statement is a script selection construct forcing the script
execution to follow different paths depending on one or several logical conditions.
If condition then

[ statements ]

{ elseif condition then

[ statements ] }

[ else
 [ statements ] ]

end if

Sub
The sub..end sub control statement defines a subroutine which can be called upon
from a call statement.
Sub name [ ( paramlist )] statements end sub

Switch
The switch control statement is a script selection construct forcing the script
execution to follow different paths, depending on the value of an expression.
Switch expression {case valuelist [ statements ]} [default statements] end switch

Visualization Expressions

An expression is a combination of functions, fields, and mathematical operators (+

* / =). Expressions are used to process data in the app in order to produce a result
that can be seen in a visualization. They are not limited to use in measures. You
can build visualizations that are more dynamic and powerful, with expressions for
titles, subtitles, footnotes, and even dimensions.
This means, for example, that instead of the title of a visualization being static text,
it can be made from an expression whose result changes depending on the
selections made.

Functions & Statements Not Recommended in Qlik Sense

Most functions and statements that can be used in QlikView load scripts and chart
expressions are also supported in Qlik Sense, but some of them are not
recommended for use in Qlik Sense. There are also functions and statements
available in previous versions of Qlik Sense that have been deprecated.
For compatibility reasons they will still work as intended, but it is advisable to
update the code according to the recommendations in this section, as they may be
removed in coming versions.
Script statements not recommended in Qlik Sense
This table contains script statements that are not recommended for use in Qlik
Sense.
Script statements that are not recommended

Statement Recommendation

Command Use SQL instead.

CustomConnect Use Custom Connect instead.

Script statement parameters not recommended in Qlik Sense

This table describes script statement parameters that are not recommended for use
in Qlik Sense.
Script statement parameters that are not recommended

Statement Parameters

Buffer Use Incremental instead of:

● Inc (not recommended)

● Incr (not recommended)

LOAD The following parameter keywords are generated by Qlik

View file transformation wizards. Functionality is retained
when data is reloaded, but Qlik Sense does not provide guided
support/wizards for generating the statement with these
parameters:

● Bottom

● Cellvalue
Script statement parameters that are not recommended

Statement Parameters

● Col

● Colmatch

● Colsplit

● Colxtr

● Compound

● Contain

● Equal

● Every

● Expand

● Filters

● Intarray

● Interpret

● Length

● Longer

● Numerical

● Pos

● Remove

● Rotate

● Row

● Rowcnd
Script statement parameters that are not recommended

Statement Parameters

● Shorter

● Start

● Strcnd

● Top

● Transpose

● Unwrap

● XML: XMLSAX and Pattern is Path

Functions not recommended in Qlik Sense

This table describes script and chart functions that are not recommended for use
in Qlik Sense.
Functions that are not recommended

Function Recommendation

NumAvg Use Range functions instead.

NumCount
NumMax
NumMin
NumSum

QliktechBlue Use other color functions instead. QliktechBlue() can

QliktechGray be replaced by RGB(8, 18, 90) and QliktechGray can
be replaced by RGB(158, 148, 137) to get the same
colors.
Functions that are not recommended

Function Recommendation

QlikViewVersio Use EngineVersion instead.

n

ProductVersion Use EngineVersion instead.

QVUser
Year2Date Use YearToDate instead.
Vrank Use Rank instead.
WildMatch5 Use WildMatch instead.

ALL qualifier
In QlikView, the ALL qualifier may occur before an expression. This is equivalent
to using {1} TOTAL. In such a case the calculation will be made over all the
values of the field in the document, disregarding the chart dimensions and current
selections. The same value is always returned regardless of the logical state in the
document. If the ALL qualifier is used, a set expression cannot be used, since
the ALL qualifier defines a set by itself. For legacy reasons, the ALL qualifier will
still work in this version of Qlik Sense, but may be removed in coming versions.

References

● https://help.qlik.com/
● https://www.qlik.com/