Qlik Community

Qlik Design Blog

All about product and Qlik solutions: scripting, data modeling, visual design, extensions, best practices, etc.

Announcements
Coming your way, the Qlik Data Revolution Virtual Summit. October 27-29. REGISTER

Set analysis is one of the more complex things you can use in QlikView or Qlik Sense. Its syntax is often perceived as complicated and there are some misunderstandings around it. So here is my short explanation.

Set analysis is a way to define an aggregation scope different from current selection. Think of it as a way to define a conditional aggregation. The condition, however, is in itself like a selection that is evaluated before the cube (the chart) is expanded. Hence, it is not possible to have a condition that is evaluated row by row.

 

The set analysis is used inside an aggregation function, e.g. in an expression like

 

          Sum(Sales)

 

The first step is to add the markers for the set analysis – the curly brackets:

 

          Sum( {…} Sales)

 

These define the record set over which the aggregation should be made. Inside, you can use different identifiers and operators, e.g. ‘$’ for records implied by current selection, ‘1’ for all records, ‘1-$’ for all excluded records, etc.

 

A set of records that you can define by a simple selection is called natural set. Not all record sets are natural; for instance, {1-$} cannot always be defined through a selection.

 

The next step is often to add a set modifier, which is defined by angle brackets. The set modifier adds or changes a selection. It can be used on any natural set and consists of a list of fields, where each field can have a new selection:

 

          Sum( {$<…>} Sales)

 

The next step is to define the element set for a field; the set of field values that defines the selection. The element set could be a field reference or a set function, P() or E(). It is more common, though, that it is an explicit list of field values or a search, and then you need the curly brackets to define the element set:

 

          Sum( {$<Date={…}>} Sales)   or   Sum( {$<Date=P(…)>} Sales)

 

A search can be defined through double quotes. This way, field values that match the search string will be selected:

 

          Sum( {$<Date={"…"}>} Sales)

 

Do not use single quotes to initiate a search here! Single quotes should denote literals, i.e. explicit field values. (Yes, today single quotes work as a search, but this is a bug that one day will be fixed…)

 

Often a numeric search is made, defined by a leading relational operator. Then, field values will be selected based on a comparison:

 

          Sum( {$<Date={"<=…"}>} Sales)

 

To make it worse, the value to which the field values are compared is often a calculated one. And in order to get a calculated value into the expression, a dollar expansion is needed.:

 

          Sum( {$<Date={"<=$(…)"}>} Sales)

 

Inside the dollar expansion, you need an expression that starts with an equals sign and contains an aggregation function, e.g.:

 

          Sum( {$<Date={"<=$(=Max(Date))"}>} Sales)

 

This aggregation function is evaluated globally, before the cube is expanded.

 

As you can see, there are many levels of a set expression, and many pairs of brackets and delimiters that need to match. When you write set expressions, you should always write both brackets directly, and then continue with the expression between them. This way you will avoid simple syntax errors.

 

Good luck with your set analysis expressions!

 

HIC

 

Further reading related to this topic:

Why is it called Set Analysis?

Dates in Set Analysis

Excluding values in Set Analysis

Introduction to Set Analysis (video) - Part 1

39 Comments
Partner
Partner

Hi Henric,

thank you for another brilliant blog post!

I have a question regarding to: "Do not use single quotes here! Single quotes should denote literals, i.e. explicit field values. (Yes, today single quotes work as a search, but this is a bug that one day will be fixed…)"

I am just going through Advanced Topics in Design and Development course book and I found the following there:

String/Numeric values

To select string or numeric values, place the value inside {} and single quotes (double quotes also work, but using them is not best practice).

=Sum({$<Year={'2011'}>}LineSalesAmount)

=Sum({$<Country={'USA'}>}LineSalesAmount)

same is then shown for Conditional values

=Sum({$<OrderDate={'>01/01/2011'}>}LinesSalesAmount)

So where is the true? Should I trust double quotes or single quotes? Can you please clarify?

Thank you for your help!

T.

15,103 Views

In all other places in QlikView/Qlik Sense, single quotes mean literals and double quotes mean something else. The intention for Set Analysis was when it was designed, to follow the same logic. However, the implementation today is that single or double quotes doesn't matter in Set Analysis. But there is a consensus in the Qlik development organization that this is a bug that should be corrected.

For the above examples, this means that

     =Sum({$<Year={'2011'}>} LineSalesAmount)

     =Sum({$<Country={'USA'}>} LineSalesAmount)

are both correct. Both 2011 and USA are literals, so single quotes are correct, if you want a case sensitive comparison.

The third example is correct if you compare how QlikView de facto works, but incorrect given the design intention. Our education department has (correctly) described how it works, but not how it should work.

I'll talk to our education department and make sure the training material is changed.

HIC

15,103 Views
Partner
Partner

Thank you Henric! It's all clear now.

0 Likes
15,103 Views
Specialist III
Specialist III
0 Likes
15,103 Views
Contributor III
Contributor III

Great! Clear explanation! Thanks.

0 Likes
15,103 Views
Not applicable

DR. Henric Cronström,

A million Thanks for your wonderful insights. This is a very important and complicated concepts and through examples you have made it clear. I highly appreciated it.

I hope to stay in touch for Data Modeling, Incremental load among other challenging questions.

0 Likes
15,103 Views