21 December 2022 Sorting data 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 sorting data in Qlik Sense. Many responses again and as expected nobody was fooled by the answers. You all got it right! The correct answer is A Sorting data When receiving data it might happen that data is unsorted. Mostly when receiving custom/hand-made files. While sorting is possible in the front end it is good practice to have the data sorted in the stored data as well. Furthermore it might happen that certain aggregations or calculations are made in the script based on a certain sorting. Here you can think of accumulating sales over time. In order to properly sort this data the order by clause can be added to the load script. Order by The order by clause is quite simple: Order by fieldname [ sortorder ] { , fieldname [ sortorder ] } You will tell Qlik to order the table based on the field given. It is possible to sort on more fields, these are added after a comma. It is also possible to influence the sort order, by specifying whether it is ascending (asc) or descending (desc). A order by on more fields based on this question could look like the following: Order by Date, Product, Price Desc This means we order the table by Date, then Product and finally Price Descending. So if we have products on the same date these are sorted from highest to lowest selling price. Things to keep in mind Order by will only work on resident tables. So first do a load from the data source and use this as a temporary table to do the sorting on. It will also not work on loads from files or as a preceding load. (for more info on preceding loads check out this blog post!) The default sort order is ascending, so numerical low to high and from alphabet a to z. It is not necessary to specify this in the order by clause, however for clarity sake it might be wise. Then use asc to specify ascending order or desc for the other way around. When making changes in the load of the resident table be aware that if you use an alias (as) you need to specify the original name of the field. The order in which you specify the order by clause determines the order in which the ordering is done. So in the example above the table will first be sorted on Date then Product and then Price descending. Keep this in mind if you get unexpected results. That’s it for this week! 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 Qlik 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