Technical Deep Dive on Qlikview 11 Development Features

Elif Tutuk

#qonnections

Legal Disclaimer

This Presentation contains forward-looking statements, including, but not limited to, statements regarding the value

and effectiveness of QlikTech's products, the introduction of product enhancements or additional products and

QlikTech's growth, expansion and market leadership, that involve risks, uncertainties, assumptions and other factors

which, if they do not materialize or prove correct, could cause QlikTech's results to differ materially from those

expressed or implied by such forward-looking statements. All statements, other than statements of historical fact, are

statements that could be deemed forward-looking statements, including statements containing the words "predicts,"

"plan," "expects," "anticipates," "believes," "goal," "target," "estimate," "potential," "may", "will," "might," "could," and

similar words. QlikTech intends all such forward-looking statements to be covered by the safe harbor provisions for

forward-looking statements contained in Section 21E of the Exchange Act and the Private Securities Litigation Reform

Act of 1995. Actual results may differ materially from those projected in such statements due to various factors,

including but not limited to: risks and uncertainties inherent in our business; our ability to attract new customers and

retain existing customers; our ability to effectively sell, service and support our products; our ability to manage our

international operations; our ability to compete effectively; our ability to develop and introduce new products and add-

ons or enhancements to existing products; our ability to continue to promote and maintain our brand in a cost-effective

manner; our ability to manage growth; our ability to attract and retain key personnel; the scope and validity of

intellectual property rights applicable to our products; adverse economic conditions in general and adverse economic

conditions specifically affecting the markets in which we operate; and other risks more fully described in QlikTech's

publicly available filings with the Securities and Exchange Commission. Past performance is not necessarily indicative

of future results. The forward-looking statements included in this presentation represent QlikTech's views as of the

date of this presentation. QlikTech anticipates that subsequent events and developments will cause its views to

change. QlikTech undertakes no intention or obligation to update or revise any forward-looking statements, whether

as a result of new information, future events or otherwise. These forward-looking statements should not be relied upon

as representing QlikTech's views as of any date subsequent to the date of this presentation.

This Presentation should be read in conjunction with QlikTech's periodic reports filed with the SEC (SEC Information),

including the disclosures therein of certain factors which may affect QlikTechs future performance. Individual statements appearing in this Presentation are intended to be read in conjunction with and in the context of the

complete SEC Information documents in which they appear, rather than as stand-alone statements.

2011 Qlik Technologies Inc. All rights reserved. QlikTech and QlikView are trademarks or registered trademarks of

Qlik Technologies Inc. or its subsidiaries in the U.S. and other countries. Other company names, product names and

company logos mentioned herein are the trademarks, or registered trademarks of their owners.

#qonnections

Elif Tutuk

Technical Product Marketing Manager

Drive and execute the go-to-market strategy for QlikViews enterprise readiness initiatives

8 years of business intelligence architect experience

QlikView addict

#qonnections

Agenda

QlikView Rapid Analytic App Platform

Comparative Analysis

Conditional Enablement of Dimensions & Expressions

Dimension Limits

#qonnections

QlikView 11 Theme:

Rapid Analytic App Platform

#qonnections

Rapid Analytic App Platform

With Business Discovery, there are no end users

QlikView 11 includes new and improved capabilities that meet the needs of IT professionals, as well as the needs of business users who

want to create their own analytic apps

Improved application

development

#qonnections

Comparative Analysis

#qonnections

Comparative Analysis: Overview

New capability for comparing sets of the data

Eliminates often used techniques involving macros, duplicated data model

Most common cases

Ad hoc groupings

Visual comparison

All work dependent on development (vs. explicit end user functions)

#qonnections

Comparative Analysis A Comparison

Method Technique Level Flexible Multiple Visibility Coverage

Set

Reference

Select,

context

menu,

select

Selection

(list box)

No. Must

clear

reference &

reset

No No End user

defined. No

Ajax

Detach/

Attach

Select,

context

menu,

select

Object No. Must clear lock

Yes No End User

Defined. No

Ajax

Bookmark Select, save.

Expressio

n

Yes. Can

update

bookmark

Yes No Developer

predefined.

End user

modified. All

clients

Alternate

State

Define

labels,

assign

objects,

make

selections

Sheet,

object,

expression

Yes. End user

can adjust

selections

independently

.

Yes Yes Developer

predefined.

End user

content. All

clients

#qonnections

Comparative Analysis How To

State Identifiers

Standard Identifiers

Define

Tie sheets & objects to Alternate States

Assign Simplify

design

Inherit

User Interactions

Use

#qonnections

Comparative Analysis - Define

#qonnections

Comparative Analysis - Assign

1. Sheet assignment

2. Container assignment

3. List box/Chart assignment

4. Expression assignment

#qonnections

Comparative Analysis - Demonstration

Simple demonstration

Existing QlikView techniques for comparing data sets

Using alternate state for comparing data sets

#qonnections

Comparative Analysis Inheritance

DOCUMENT (Default Only)

#qonnections

Comparative Analysis Inheritance

SHEET (Default, Inherit, Named)

#qonnections

Comparative Analysis - Inheritance

CONTAINER (Default, Inherit [Sheet], Named)

#qonnections

Comparative Analysis - Inheritance

SHEET OBJECT/CONTAINED OBJECT

(Default, Inherited, Named)

#qonnections

Comparative Analysis - Inheritance

EXPRESSION (Default, Inherited [Object], Named)

#qonnections

Alternate States New Function

Testing for a State

Conditioning elements on an alternate state thru a new function

Statename()

Dynamic Text ='Region - ' &if(StateName() = '$', 'Default', StateName())

Dynamic Colors if(StateName() = 'Group 1', rgb(152, 171, 206),

if(StateName() = 'Group 2', rgb(187, 200, 179),

rgb(210, 210, 210)

)

)

Examples

#qonnections

Comparative Analysis Additional

Clear

Affects all states or can be selective via new menu off CLEAR button

State Navigation & Lock/Unlock

All states

Linked Objects

If the copied object has a setting of INHERIT, it may perform differently in another location (sheet/container)

WHY?

#qonnections

Comparative Analysis & Expressions

Alternate States extend existing set analysis syntax

V10 Set Analysis allows you to reference certain states

$, 1, $_x, x_$

Bookmarks

New V11 allow reference to an Alternate State per expression

Allows comparisons between measures with reference to dynamic groups

New syntax

Function ({[state_identifier]} field_name)

Looks like standard set syntax

But new syntax to reference fields between states

Function ({[state_identifier1]} field_name3)

#qonnections

Alternate States - Syntax

Function ({[state_identifier1]} field_name)

Perform aggregation function on field for selections

based on state labeled [state_identifier1].

e.g. sum({$} Sales)

e.g. sum({Group1} Sales)

e.g. avg({MarketDev} SalesLeadTime)

#qonnections

Alternate States - Syntax

Function ({[state_identifier1] } field_name)

Set values for field_name2 within [state_identifier1] based

on hard coded value.

Standard set analysis syntax for set modifier

e.g. sum({Group1} Sales)

e.g. avg({MarketDev} SalesLeadTime

#qonnections

Alternate States - Syntax

Function ({[state_identifier1] } field_name)

Set values for field_name2 within [state_identifier1]

based on values of field_name3 in [state_identifier2]

e.g. sum({Group1} Sales)

e.g. avg({MarketDev} SalesLeadTime

Option 1 - sum({[Group 1]} Sales)

Option 2 - sum({$} Sales)

Achieving the same thing with 2 different syntax:

#qonnections

Alternate States - Syntax

Function ({[state_identifier1]::bookmark1} field_name)

Perform aggregation function on field for selections based on

applying selections stored in bookmark 1 for state 1

e.g. sum({Group1::Baseline} Sales)

e.g. avg({MarketDev::MarketNorm} SalesLeadTime)

You cannot reference a field in a bookmark you are applying the

entire bookmark against the state.

#qonnections

Exercise

1. Setup a dashboard that

allows a user to highlight

(brush) subsets of products within the

overall product and see

their performance against

the main set.

1. Modify AltState-EX1

2. Have selection vs. others

transposed on top of one

another

3. Show Current Selection

for all selection states

#qonnections

Questions

#qonnections

Conditional Enablement of Dimensions &

Expressions

#qonnections

Conditional Enablement of Dimensions & Expressions:

Overview

Often requested enhancement to set calculation string for each dimension and expression in any chart

More powerful than simple Show Condition (straight table only)

Flex layout of sheet objects based on current environment

Lets take a look

#qonnections

Demo: Conditional Enablement of Dimensions &

Expressions

Setup condition on dimension within a chart

Setup condition on an expression within a chart

In conjunction with Show Condition

#qonnections

Conditional Enablement

Implications

Toggling object layout can introduce complexity into design/debugging

Requires more rigor in testing conditions

Potential performance hit change calculation, clear cache

But potential macro code & object reduction

Current solutions to this problem have often duplicated objects and controlled hide/show of the object based on conditions

Fewer objects, better performance

Reduced macro code, better management & performance

Reduced column calculations, better performance

Overlap with Show Condition in Straight Tables

Performance impact of radically different dim/exp permutations

#qonnections

Exercise

1. Make a chart in

document CONDITION-

DIMEXP EX1 that allows the user to

dynamically select which

dimensions &

expressions comprise the

chart.

Make this!

#qonnections

Questions

#qonnections

Dimension Limits

#qonnections

Dimension Limits: Overview

New capabilities for a chart to show totals, other segments and limit to top/bottom performing dimension values

Moves these features into the calculation engine vs. the presentation layer

Consistency across charts

New capabilities will simplify numerous chart acrobatics from earlier releases

#qonnections

Dimension Limits Sample Applications

Have you ever tried to ?

Restrict a table or chart based on a the contribution of a dimension to the total?

Summarize non-displayed dimensions as OTHERS without resorting to a pie chart?

Evaluate lower level dimensions either locally or globally? Use these as qualification criteria to determine what to display in table or chart?

#qonnections

Dimension Limits

Dimension totals Restrict

dimension display

based on flexible

criteria

Include an all

other dimension

Treat sub-

dimensions as

local or global

#qonnections

Dimension Limits - Configuration

#qonnections

Dimension Limits - Considerations

Pivot Tables and Gauge Charts do not include dimension limits

When working with multi-dimension charts

Consider that limits are set at the individual dimension level

Limits are not applied at the intersection of dimensions

See Accumulated Values (Intersection Design)

Sort order has significant impact

When using FIRST values

May want to turn off INTERACTIVE SORT to prevent end users getting different results

Migration Implications

Presentation Settings

Pie Charts

Straight Table vs. Pivot Table

#qonnections

Exercise -

1. In doc DIM-LIM-EX1 take the basic straight table and create

1. Chart showing top 45% margin contributing sales people

2. Chart showing top 2 regions and within each region performance of top 4 products across entire company

3. Chart showing customer sales for all orders that are less than $150 (in total value)

#qonnections

Questions

#qonnections

Summary

Comparative Analysis

Conditional Enablement of Dimensions & Expressions

Comparative Analysis & Conditional Enablement

Dimension Limits

Examples are available on QlikCommunity

#qonnections

Stay Qonnected

Visit partners.qlikview.com

to download all Qonnections

2012 presentations

Join the conversation

Qonnections Community

Group tinyurl.com/qonnect-qlikcommunity

Qonnect Facebook Group tinyurl.com/qonnect-facebook

Qonnect LinkedIn Group tinyurl.com/qonnect-linkedin

#qonnections

Stay Qonnected

Elif Tutuk

Technical Product Marketing Manager

QlikTech, Inc.

elif.tutuk@qlikview.com

+1 (408) 368-4333

elif.tutuk

Thank you!