14 March 2022 Unpivot data in Qlik with the CrossTable prefix 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 how to unpivot data in Qlik: The answers to this question were unanimous, and you were right: The correct answer is answer B: CrossTable(Quarter, Budget, 2) Since the pivot table is a great way to analyze data in excel, it is just a matter of time before you will come across one. Contrary to a straight table, it consists out of grouped values in which you can expand the rows as you please to show more detailed aggregations. However, the format of a pivot table makes it less than ideal for integrating directly into your data model. You will have to ‘unpivot’ the values. Unpivot data with the CrossTable prefix This is done by using the CrossTable prefix. But how does this work? Let’s have a look at the table loaded into the example: The values are aggregated by Channel, Region and Quarter, where the quarters are shown in individual columns. If we load this table directly into Qlik without any transformations, we get a separate field for each quarter named 2022-Q1, 2022-Q2, etc, making this not an ideal way for an end user to analyze. So how do we solve this? As mentioned before the CrossTable Prefix. If we look at the official Qlik documentation the prefix is used as following: crosstable (attribute field name, data field name [ , n ] ) ( loadstatement | selectstatement ) There is an attribute field name, consisting of the attribute values, A data field name, consisting of the data values, And n, consisting of the number of qualifying fields preceding the table to be transformed. So how does it work? A lot of theory, but how does this work in practice? Let’s make things a bit more clear by taking the example table from the question, labeling the relevant columns and cells and unpivoting the data. The schematic below shows how this works: The labels for the different quarters, 2022-Q1, 2022-Q2, etc. become the contents for the attribute field Quarter. The values in the columns 2022-Q1, 2022-Q2, etc. become the content for the data field Budget. The names of the attribute and data fields can be arbitrarily chosen. We used Quarter and Budget because these best describe the contents of the fields. The first 2 columns, Channel and Region do not need to be transformed. We specify the value 2 for the number of qualifier fields. This means that only the columns after the first 2 columns will be ‘unpivoted’. This leads to the following prefix: CrossTable(Quarter, Budget, 2) That’s it. We look forward to seeing your comments and hope to see you again next Friday! More from the Bitmetric team Qlik Cloud Backup Protect your investment in Qlik with daily incremental backups stored in an encrypted environment with redundant storage. Available for as little as 2 Euro per day. Learn more. Masters Summit for Qlik The Masters Summit for Qlik provides the next step in your path to becoming a Qlik specialist. As an extra perk, Bitmetric has secured an over $450 discount just for you! Use code BITMETRIC at checkout. Read more here. Data Model Friday Qlik Test Prep Script Solution How can we help? Barry has over 20 years experience as a Data & Analytics architect, developer, trainer and author. He will gladly help you with any questions you may have. Call us Mail us 17 September 2025 Qlik vs Power BI: Part 4 – End User Interaction & Integration Part 4 of our Qlik vs Power BI series compares the end-user experience, examining navigation, selections, filters, drill-downs, and integration, and how each tool supports or complicates user interaction. Power BI Qlik 11 September 2025 Qlik vs Power BI: Part 3 – Front End Development & User Experience Part 3 of our Qlik vs Power BI series explores Qlik’s grid responsive layout and associative model versus Power BI’s precision layout and query-based interactions, highlighting their impact on dashboard design and user experience. Power BI Qlik 4 September 2025 Qlik vs. Power BI: Part 2 – Back-End & Data Modeling This post is Part 2 of our series on Qlik vs Power BI data preparation and modeling. We compare Qlik’s structured, script-driven approach with QVDs to Power Query’s flexible, user-friendly interface, and explain what each means for building reliable data models. Power BI Qlik
17 September 2025 Qlik vs Power BI: Part 4 – End User Interaction & Integration Part 4 of our Qlik vs Power BI series compares the end-user experience, examining navigation, selections, filters, drill-downs, and integration, and how each tool supports or complicates user interaction. Power BI Qlik
11 September 2025 Qlik vs Power BI: Part 3 – Front End Development & User Experience Part 3 of our Qlik vs Power BI series explores Qlik’s grid responsive layout and associative model versus Power BI’s precision layout and query-based interactions, highlighting their impact on dashboard design and user experience. Power BI Qlik
4 September 2025 Qlik vs. Power BI: Part 2 – Back-End & Data Modeling This post is Part 2 of our series on Qlik vs Power BI data preparation and modeling. We compare Qlik’s structured, script-driven approach with QVDs to Power Query’s flexible, user-friendly interface, and explain what each means for building reliable data models. Power BI Qlik