28 September 2022 Qlik subroutine parameters – passing arguments by reference and by value Share this message Every Friday at Bitmetric we’re posting a new Qlik certification practice question to our LinkedIn company page. Last Friday we asked the following Qlik Data Architect certification practice question about passing arguments to Qlik subroutine parameters: This proved to be a harder question than expected, as only a single person got the right answer. Well done Vaibhav Sharma! The correct answer is B: lines 4 and 8 both show the value 8 We’re modifying the parameter called pInput and somehow this also affects the variable vNumber? How is that possible? The explanation is that we passed the argument by reference instead of by value. In short, when we pass by value we provide a copy of the variable, but when we pass by reference we provide the actual variable to the subroutine. Read on to get a more in-depth explanation. Sidebar: argument vs parameterThese terms are often used interchangeably, but they actually do have different meanings. A parameter is the name that is listed in the subroutine definition. In this example that’s pInput. An argument is the value that’s actually supplied. In this example that’s vNumber. How variables are stored in memory To explain the difference between passing by value and passing by reference we first need some basic knowledge of how memory works. We’ll use a simplified explanation for this, which should be enough to understand the basic concept. You can consider memory as a collection of blocks that can hold data. Each block has an address, numbers 1 through 60in the illustration below. When you store a value into a variable, your operating system will automatically decide where to place this in memory. In the illustration below, the value we’ve set for the vNumber variable is stored at memory address 32. Pass by value When we pass by value, the value is copied to another location in memory. In the illustration below a copy of the value is placed at memory address 24. Subsequent operations, such as the multiplication in the subroutine, are performed on the copy. The original value is left untouched. Pass by reference When we pass by reference, we pass a reference to the memory address of the variable. What this means in our example is that both vNumber and vInput now reference the same memory space and value within that space. Any operation that is performed to pInput updates the same value that is being referenced by vNumber, and vice versa. This explains the behavior that we see in the example script. Passing by value vs passing by reference in Qlik So how can we fix this script to ensure that vNumber is passed by value? By using Dollar-sign expansion! This passes the value of the variable to the subroutine, rather than a reference to the variable. See the updated script below, with a change on line 9. That’s it for this week. See you next Friday? More from the Bitmetric team Bitmetric Qlik Support Keep your Qlik environment running smoothly with proactive support that prevents issues before they appear. Available on flexible monthly plans. Learn more. Qlik vs Power BI Series See how Qlik and Power BI perform when theory meets reality. Three apps rebuilt, every step examined. Learn more. Friday Qlik Test Prep Script Solution How can we help? Whether something’s still unclear or you’re ready to take the next step, Barry and Eric are happy to talk it through. Email us, call us, or book a meeting at a time that works for you. Call us Mail us 1 September 2026 Qlik Answers review: What we learned from real-world testing We tested Qlik Answers on a real production sales model to see how it handles real-world analytics. The results were promising, but getting reliable answers required careful work on the logical model, master measures, dimensions and business context. AI Data Analysis Qlik Semantic Layer 25 August 2026 Your semantic layer is becoming the API for AI Semantic layers are not new, but AI is giving them a new role. Where they once primarily powered dashboards, semantic models are increasingly becoming the layer that provides AI with reliable business context. AI Data Governance Microsoft Fabric Qlik Semantic Layer TimeXtender 17 August 2026 Putting AI to work on your data works. But not like this. Putting AI to work on your data sounds simple. But what can we learn from organizations already doing it? Based on Anthropic’s experience and independent research: what works, what doesn’t, and why maintenance is where the real work lies. AI Data Governance Data Management Power BI Qlik
1 September 2026 Qlik Answers review: What we learned from real-world testing We tested Qlik Answers on a real production sales model to see how it handles real-world analytics. The results were promising, but getting reliable answers required careful work on the logical model, master measures, dimensions and business context. AI Data Analysis Qlik Semantic Layer
25 August 2026 Your semantic layer is becoming the API for AI Semantic layers are not new, but AI is giving them a new role. Where they once primarily powered dashboards, semantic models are increasingly becoming the layer that provides AI with reliable business context. AI Data Governance Microsoft Fabric Qlik Semantic Layer TimeXtender
17 August 2026 Putting AI to work on your data works. But not like this. Putting AI to work on your data sounds simple. But what can we learn from organizations already doing it? Based on Anthropic’s experience and independent research: what works, what doesn’t, and why maintenance is where the real work lies. AI Data Governance Data Management Power BI Qlik