Best way to count keys? Don’t.
Read MoreSimplify with Preceding Load
Read MoreUnderstanding Join and Concatenate
Read MoreBOQC: Flexible Interval Classification
Read MoreAnalyzing Field Usage in a QVW
Read More
Blog
I was recently reviewing a problem where a chart Count() function produced differing results between QV 8.5 and 9. The field being counted was a key field. Counting a key field without using DISTINCT, especially a one-to-many key, can produce ambiguous results and should be avoided. The recommended approach is ...
Most QV script developers are introduced to “preceding load” as a LOAD that precedes an SQL SELECT. But a LOAD may also precede another LOAD, which can be a very useful tool. Let’s review a typical preceding load. Table1:LOAD Customer, Sales, today(1) as LoadDate ;SQL SELECT Customer, Country, Sales FROM ...
The Qlikview script functions JOIN and CONCATENATE can sometimes be used to tackle the same problem, but there are important differences that should be understood. Examine the sample tables below. Note that they share one common field name, “Key”. Also note that Table1 has a Key value “3” that is ...
Another post in the “Best of QlikCommunity” series.In this QlikCommunity Forum thread the poster asked about using the class() function to create a dynamic dimension of 30 minute intervals in a chart. He wanted to format the class values as display friendly time ranges. My solution would have been to ...
Wouldn’t it be nice to know what fields are “unreferenced” in your document? By unreferenced, I mean fields that are not used in Expressions, Dimensions or Keys. These are fields that if removed from your document, would have no impact on the visible elements of the application. Removing unused fields ...
