12 May 2022 Using the subset ratio in Qlik to spot errors in key fields 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 subset ratios in Qlik Sense: The correct answer is C: 28% of the CustomerID’s have never placed an order To validate and check the quality of the data model which you have just created, the data model viewer is an important tool. One of the things you can check here is the subset ratio. The subset ratio is the percentage of present distinct values within that table compared to the total distinct values of the chosen field in the whole data model . To demonstrate this see the following image: In the image above we have selected the key field CustomerID in the Sales table. We can see in the bottom half of the screen that the field CustomerID has a total of 100 distinct values in all tables in the model, not just in the selected table, visible as Total distinct values. By selecting this field within the Sales table however, we see that there are 72 distinct values in this table alone, visible as the Present distinct values. So of all 100 distinct CustomerID’s within all tables we now know that there are 72 distinct CustomerID’s in the Sales table. So by diving these we will receive the subset ratio: Present distinct values / total distinct values = 72 / 100 = 0,72 or 72% Now knowing that there is a total of 100 values this means that the Customer table must be filled with 100 distinct CustomerID’s. Having a look in the data model viewer confirms this: There are 100 distinct values present in the Customer table. Now by subtracting the 72% of the Sales table of the total 100% we end up with 28% of CustomerID’s in the total model (in this case all present in the Customer table) which have never placed an order. Other things to keep in mind Some other things to keep in mind about the subset ratio: What if the subset ratio of the dimension table is also lower then 100%? If this amount would have been lower there would have been a discrepancy between the Customer table and the Sales table in which both tables would have had values not present in the other. For a fact table it is not uncommon to have a subset ratio of lower then 100%, however a dimension table, like the Customer table in the example, with a subset ratio of less then 100% means that you should have a look at the data in the model. If for example the subset ratio in the Customer table would have been 90%, it means that we have 10% of distinct CustomerID’s present in the Sales table, which are not being matched with a CustomerID in the Customer table. What if the total of the subset ratio’s is 100%? If the combined total of the subset ratio’s of all tables would be 100% it means that there are no matching values between the tables. Good luck 😉 FAQ How do you address or correct the errors once a low subset ratio is identified? Addressing or correcting the errors identified by a low subset ratio in Qlik Sense or QlikView typically involves a manual review of the data model and the relationships between tables. Once a low subset ratio is identified, indicating discrepancies or missing data, users should examine the key fields and relationships to understand the cause of these discrepancies. This might include checking for incorrect key field associations, missing entries, or data quality issues in the source data. Corrective actions can vary, ranging from modifying the data load script to adjust how tables are joined, correcting data entry errors in the source data, or redefining relationships within the data model to ensure all relevant data is accurately associated. Are there any tools or features within Qlik Sense or QlikView that automatically fix or suggest fixes for discrepancies highlighted by the subset ratio? Qlik Sense and QlikView do not have built-in tools that automatically fix discrepancies highlighted by the subset ratio. However, they offer robust data modeling and scripting capabilities that allow users to manually address and rectify these issues. Users can leverage the data model viewer and the script editor to make adjustments and improvements to the data model. Additionally, Qlik’s community forums and documentation provide extensive resources and examples on how to handle common data modeling challenges. How does the subset ratio impact the performance and accuracy of data analysis in Qlik Sense or QlikView? The subset ratio’s impact on the performance and accuracy of data analysis in Qlik Sense or QlikView is significant. A low subset ratio can indicate that not all data is being correctly associated, which may lead to incomplete or inaccurate analysis outcomes. For instance, if customer IDs are not matching correctly between tables, sales analysis could miss out on certain transactions, leading to underreported sales figures. Furthermore, discrepancies in key field associations can lead to performance issues, as the data model might be more complex or less optimized than intended. Ensuring a high subset ratio, where appropriate, helps in maintaining the integrity and reliability of the data analysis, enabling more accurate and efficient reporting and insights. 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. Data Model Friday Qlik Test Prep 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