Summary: Preceding load used to slow down your script. but no more. Beginning with QV Nov 2017, preceding load has no performance penalty. I’ve posted several times about the elegance of preceding load. I’ve also written about how preceding load can make your script run significantly slower. Good news! Beginning with QV release Nov 2017 (12.20) … Continue reading Preceding Load Performance Update
Important Note: The performance penalty discussed below was fixed in the Nov2017 release. There is no longer a penalty when using Preceding Load. Summary: While preceding load is a powerful tool, the current performance penalty may cause you to reconsider using it for anything but the smallest of data sets. I’m a big fan of the … Continue reading The Cost of Preceding Load
I love the preceding load feature of Qlikview scripting. It can make complex things simple. Consider for example, having to parse an arbitrary number of key:value pairs from input like: Name:Shoes, Size:L, Color:Blue Suede, Stock: 200 Name:Socks, Model:Mens Casual, Stock:0, Color:Black Name:Pants, Error: No attributes found We want each key to become a Field populated … Continue reading Preceding Load is Elegant
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 SalesResults ; The absence of … Continue reading Simplify with Preceding Load
Here’s a fun Friday post. As I was updating my incremental load materials for the upcoming October/November Masters Summit for Qlik, I ran across an old note about creating “Attributes” in QVDs using Tags. Due to a bug in QVD generation I couldn’t implement the idea at the time. But the bug is long since … Continue reading Using Attributes in QVD Files
Summary: I offer some tips for writing better performing and easier to maintain syntax when using the Qlik If() function. The Qlik If() function is very powerful and frequently appears in Qlik Sense and QlikView apps. Expressions using multiple If() functions can easily get out of hand and become difficult to maintain or debug, as well as … Continue reading If() Tips
Summary: I review using Join, Lookup() and ApplyMap() as script techniques to calculate using fields from multiple tables. I ultimately recommend ApplyMap(). Qlik charts can calculate values on the fly, using fields from multiple tables in the model. The associative model takes care of navigating (joining) the correct fields together. Our expression syntax doesn’t identify what table a field exists in … Continue reading Creating Temporary Script Associations
TLDR: A new Qlik Sense training video uses a tired old-school Master Calendar script. I propose that updated training materials should use an updated script. I just watched a new video by Michael Tarallo of Qlik titled “Understanding the Master Calendar – Qlik Sense and QlikView“. Before I pick on the contents of this particular video, I … Continue reading Better Calendar Scripts
As a QV Consultant, I split my time between delivering training and QV Practice. I like both sides of the business, but I particularly enjoy contributing to the excitement of using QV that results from training. During a lunch break today, I mentioned the Masters Summit for Qlikview to one of my students. He asked … Continue reading Becoming a Scripting Ninja
