Qlik Workshop #13: Calculation Strategy
Why do some Qlik apps feel buttery smooth while others crawl the moment you add a few KPIs? 😅
In Week 13 of the Arc Academy Workshop Series, JC Zientek and Austin Spivey break down calculation strategy—how and where to place your logic so your apps stay fast, scalable, and easy to work with.
You’ll see how set analysis actually works under the hood, when to put logic in the script vs. front end, and how to balance performance with developer agility.
If you’ve ever wondered, “Should this be in the load script or in a set analysis expression?”, this one’s for you. 🚀
🔑 Key Takeaways
💡 Where You Put Logic Matters
Understand how moving calculations between back end (script/QVD) and front end (charts) changes app performance.
🧠 Set Analysis = Front-End WHERE Clause
Treat set analysis as the “WHERE clause of the front end” to filter and slice data without extra fields.
📚 Structuring Logic Across Layers
Learn how to spread logic across script, QVDs, and app front end to handle large models and high cardinality cleanly.
⚡ Symbol Tables & Numeric Values
See how Qlik’s symbol tables and numeric keys drive evaluation speed—and why that matters for heavy calculations.
⚖️ Balancing Reactivity vs. Load Times
Find the sweet spot between super‑reactive front‑end logic and strong back‑end pre‑processing.
🛠️ Practical Dev Tips
Use set analysis for rapid iteration and testing, then know when to “graduate” logic into the script for better performance.
Chapters:
00:00 – Intro
00:04 – Welcome to Week 13: Calculation Strategy
01:06 – Enterprise‑scale considerations for Qlik deployments
02:08 – Set analysis as the “WHERE clause” of the front end 🧠
03:31 – Back‑end vs front‑end logic for set analysis
04:13 – Syntax, complexity & common gotchas
05:30 – Understanding performance implications ⚡
06:31 – How set analysis works under the hood (symbol tables, evaluation)
08:03 – Demo: ACT score calc with vs without set analysis
10:28 – Balancing performance and reactivity in real apps ⚖️
11:47 – Why heavy front‑end set analysis can slow down apps
13:22 – Developer advantage: fast iteration with set analysis
14:26 – Finding the sweet spot: back‑end vs front‑end calculations
17:37 – Wrap‑up & key takeaways
🔗 Links & Resources
🌐 Website: https://arcanalytics.co/
🔗 LinkedIn: / arcanalytics
▶️ YouTube: / @arcanalytics
📘 Facebook: https://www.facebook.com/profile.php?...
👥 Skool Community (Arc Academy for Qlik): https://www.skool.com/arc-academy-for...
🤝 Qlik Partner Profile: https://qlik-partners.com/locator/#/2...
📷 Instagram: / arcanalytics
🆓 Free 30-Day Qlik Trial: https://www.qlik.com/us/trial/partner...
Qlik Cloud, Qlik data modeling, Qlik Sense data model, data modeling strategy, associative engine, star schema vs flat table, RAM optimization, data cardinality, Qlik performance, enterprise data architecture, data quality, data integration, QVD, ETL, CDC streaming, data warehouse, data lake, analytics architecture, business intelligence, data governance, scalable dashboards, intermediate Qlik training, Arc Academy, Arc Analytics
#QlikCloud #QlikSense #DataModeling #DataStrategy #BusinessIntelligence #DataAnalytics #DataQuality #AssociativeEngine #ETL #DataArchitecture #ArcAcademy #ArcAnalytics #QlikTraining #AnalyticsEngineering