20 July 2022 What is the difference between the Alt and Coalesce functions in Qlik Sense? 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 the Alt() and Coalesce() functions in Qlik Sense, and how they differ from each other: The correct answer is B: Coalesce(SizeName, ’Unknown’) AS SizeName The disparity between the answers this week shows that this function is not well known yet, but Coalesce() has made it to Qlik in recent years. And being the correct answer in this question, why is the answer Coalesce() and not any of the others? The difference between Alt and Coalesce in Qlik The main difference between Alt() and Coalesce() is that Coalesce() returns the first non-null value of the given statement, while Alt() returns the first valid number representation. In this case we are looking to fill a text value (small, medium and large) and not a number, so Alt() will not work. Before Coalesce() was added to Qlik, the go to solution would be to write an If-statement to check for empty values, the solution being something almost equal to answer C. However in this example the else statement of the If() expression is omitted, by which we only get ‘unknown’ as result and not the original SizeName. The proper expression should be: If(IsNull(SizeName), ‘Unknown’, SizeName) AS SizeName. Concluding, the Coalesce() function is the more elegant solution in this case. Using just Coalesce(SizeName, ‘Unknown’) AS SizeName. The syntax for Coalesce is as following: Coalesce(Expr1, [Expr2, Expr3, ....], else) For Coalesce() it is possible to give unlimited arguments to compare. When all of these arguments return null the final position in the syntax can be used to give a return value. In the question ‘Unknown’ was used, so we can quickly select this in the front end to check the overall data quality. Other things to consider when using Coalesce() One thing to note is that Coalesce() makes for a great combination with EmptyIsNull(). Since Coalesce() returns the first non null value, we need to make sure that all values are true null. Using EmptyIsNull() transforms all empty values into a null value. So instead of long strings like, IF(LEN((SizeName) = 0, Null(), SizeName) you could use Coalesce(EmptyIsNull(SizeName), ‘Unknown’). 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 Functions 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 6 November 2026 Qlik Cloud overage: who decides how much risk you face? A small error in Qlik Cloud can lead to unexpected overage charges. But how large can that financial risk become? We share our own experience, explain how Data for Analysis overage works, and discuss why customers should be able to decide how much additional capacity they want to allow. We also look at ways to prevent overages and at developments surrounding Usage Bank. Data Analysis Governance Qlik 6 November 2026 Microsoft Fabric and Power BI: The Most Important Updates from October 2026 AI agents that build Power BI reports, independently perform data engineering, and provide increasingly accurate answers to questions about business data. In October, Microsoft once again made significant progress with Fabric and Power BI. But what do these developments mean in practice? We discuss the most important updates and share our experiences and insights. Agentic […] Microsoft Fabric Power BI 4 November 2026 Qlik Cloud Update October 2026: Semantic Models, AI, and Modern Development October brought 24 updates to Qlik Cloud. The introduction of Semantic Models in Data Products stands out in particular. Qlik Code for VS Code, AI-assisted development, and improvements to the Direct Access gateway also deserve attention. Our consultants discuss what these developments mean in practice. Qlik
6 November 2026 Qlik Cloud overage: who decides how much risk you face? A small error in Qlik Cloud can lead to unexpected overage charges. But how large can that financial risk become? We share our own experience, explain how Data for Analysis overage works, and discuss why customers should be able to decide how much additional capacity they want to allow. We also look at ways to prevent overages and at developments surrounding Usage Bank. Data Analysis Governance Qlik
6 November 2026 Microsoft Fabric and Power BI: The Most Important Updates from October 2026 AI agents that build Power BI reports, independently perform data engineering, and provide increasingly accurate answers to questions about business data. In October, Microsoft once again made significant progress with Fabric and Power BI. But what do these developments mean in practice? We discuss the most important updates and share our experiences and insights. Agentic […] Microsoft Fabric Power BI
4 November 2026 Qlik Cloud Update October 2026: Semantic Models, AI, and Modern Development October brought 24 updates to Qlik Cloud. The introduction of Semantic Models in Data Products stands out in particular. Qlik Code for VS Code, AI-assisted development, and improvements to the Direct Access gateway also deserve attention. Our consultants discuss what these developments mean in practice. Qlik